Hi.
I don't really got what u asked, and please excuse my poor knowledge and skip this post, in case it's not u were looking for.
An example of JMS usage might be this: supposing u have 2 applications, one sends requests to the the other. If these requests are "getters", than u should use
Java sesssion Beans, because u need that answer answer (get a customer address).
But if these requests are "updates" or "creates" (change customer's address), than u are not interested in the response of the second application, because if they fail, a system administrator can look at those fails, see why they failed, and resubmit them in some cases.
That would imply, of course, to have an error queue (or topic), but that's different topic.
These 2 applications might not have anything in common, so that's why you may not be interested if a flow failed or not. Maybe the second application is down for some time (but it will start again), but the first application might have no ideea about this, and you may not be able to change not even a line of code in these applications.
If you put a JMS server between those 2 applications, then your problems might be solved.
about an example of JMS, I would suggest u, from my poor knowledge, to use the examples from the example directory of your JMS server, because there are differences (it happened to me from Sun's
J2EE server, different versions, as well as between Weblogic different versions).
Best regards, Tibi
