posted 18 years ago
I have an application, which is basically combination of two different applications. A application is a third party software, which comes to my application B on to do some work, which A can't do. When appication B invokes app. A. A is a modal dialog application.. couple of screens to navigate and finally when user clicks "done" button on app. A's last page. It saves data in app. A's database, calls service of B (this service eventually reads data from A database).
After above steps, App. B takes over the control and there is a workflow process involved before things are said to be done in B. Now in some of the cases there is no workflow involved and as soon as user hits done on App. A, calls B's service, App. B should refresh its page with updated data.
Here to handle db, network etc. failure I am thinking to use JMS. App A would always put messsage in queue, App B would read it upon receipt in queue. Now as I said earlier there are some cases when there is no workflow involved where user (who is in App. B). Needs to see results right away as soon as he/she clicks "done" on app. A.
Since JMS would be in place, user won't be able to see his/her changes right away on UI until app. B consumes the message. Architecture wise this should be okay but from user perspective, this doesn't look so right. This is very critical and important issue for us and me to figure it out. Anyone has any ideas of how to achieve this? If not JMS, what else?
Thanks,