You are right.
The jms flow will need the J2EE container to host a ServiceMix instance
(even if there is no component deployed inside it).
If this is what you want to avoid, the two main solutions are HTTP and JMS.
If you want to have asynchronous, reliable communications, just use JMS
(you can still use non-persistent messaging).
Cheers,
Guillaume Nodet
On 6/1/06, jnordstrom <[EMAIL PROTECTED]> wrote:
Hi Jordan,
Thanks for the reply; I thought JMS Flow was used to bridge ESB
containers?
Correct me if I am wrong. I'm not sure how this would work for a J2EE
application. I was thinking of using an asynchronous request/reply model
to
interact with the ESB, using a JMS client to send request and Message
Driven
POJOs to read the response, but am questioning the use of messaging just
to
have two VM communicate.
I do plan on using JMS Flow or something similar for the node to
node
communication.
James
--
View this message in context:
http://www.nabble.com/J2EE+to+ESB+communication+on+a+single+node+%28Two+Virtual+Machines%29-t1718300.html#a4668386
Sent from the ServiceMix - User forum at Nabble.com.
