Re: [service-orientated-architecture] Re: Client Side Invocation Frameworks?

[William Henry]

This is the same problem that occurred in CORBA. Before CORBA 2.0 each vendor had their own on-the-wire format. CORBA 2.0 introduced IIOP. This gave users of CORBA far more options and  kept them from forced vendor lock-in. I'm actually surprised that JMS has gotten away with this for so long. One would think that the Java community  would have fixed this issue long before now. Then again it seems that in the software, and particularly the middleware, fashion industry we like to reinvent technology and technology cycles again and again and again ........ William On Aug 26, 2006, at 1:37 PM, Eric Newcomer wrote: Yes, and this is exactly why we are working on AMQP...    Once both JMS vendors support AMQP they they will be able to talk to each other.   Eric ----- Original Message ---- From: Stefan Tilkov <stefan.tilkov@innoq.com> To: service-orientated-architecture@yahoogroups.com Sent: Saturday, August 26, 2006 3:05:14 PM Subject: Re: [service-orientated-architecture] Re: Client Side Invocation Frameworks? On Aug 26, 2006, at 5:56 PM, Gregg Wonderly wrote: > I can only suppose that you know something that I don't know, such > as the date > that JMS will no longer work to allow messaging between so equipped > Java > programs? Gregg: Two programs that use JMS *can't* talk to each other just because they're both using JMS. They can only talk to each other when they're using the same JMS implementation. Stefan -- Stefan Tilkov, http://www.innoq. com/blog/ st/ __._,_.___ SPONSORED LINKS Computer software program Computer software spy Computer job Database software Discount computer software YAHOO! GROUPS LINKS  Visit your group "service-orientated-architecture" on the web.    To unsubscribe from this group, send an email to:  [EMAIL PROTECTED]    Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. __,_._,___