Comments on: SOAP over JMS? http://www.subbu.org/blog/2005/03/soap-over-jms Mon, 06 Feb 2012 19:04:25 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Subbu Allamaraju http://www.subbu.org/blog/2005/03/soap-over-jms/comment-page-1#comment-96188 Subbu Allamaraju Mon, 18 Oct 2010 16:04:58 +0000 http://wp.subbu.org/2005/03/soap-over-jms/#comment-96188 Note that JMS is an API and not a protocol. Unless you standardize on a single implementation of JMS, sending SOAP messages over JMS does not buy you much. Note that JMS is an API and not a protocol. Unless you standardize on a single implementation of JMS, sending SOAP messages over JMS does not buy you much.

]]> By: James http://www.subbu.org/blog/2005/03/soap-over-jms/comment-page-1#comment-95504 James Fri, 15 Oct 2010 02:33:45 +0000 http://wp.subbu.org/2005/03/soap-over-jms/#comment-95504 Shaurabh Bharti, Here is a good link that provides a SOAP over JMS implementation in WebSphere Studio. http://www.ibm.com/developerworks/websphere/library/techarticles/0402_du/0402_du.html Keep in mind that the W3C specification is not yet finalized. I talked with the IBM folks in the UK and there are some minor coding changes that need to be done to get the latest spec implemented in WAS. Apache CFX is under way from an implementation perspective too. Shaurabh Bharti,

Here is a good link that provides a SOAP over JMS implementation in WebSphere Studio. http://www.ibm.com/developerworks/websphere/library/techarticles/0402_du/0402_du.html

Keep in mind that the W3C specification is not yet finalized. I talked with the IBM folks in the UK and there are some minor coding changes that need to be done to get the latest spec implemented in WAS. Apache CFX is under way from an implementation perspective too.

]]> By: Shaurabh Bharti http://www.subbu.org/blog/2005/03/soap-over-jms/comment-page-1#comment-36 Shaurabh Bharti Wed, 31 May 2006 00:25:37 +0000 http://wp.subbu.org/2005/03/soap-over-jms/#comment-36 SOAP over JMS does makes sense a lot! Actually, within smaller network (as said in 1st reference), it makes a lot of sense to use JMS for reliable messaging. However, in bigger networks as HTTP is quite default and easy supported by servers (which might not be case by all servers), hence, jms-http-http-jms is no bad soln. I'm looking for an example implementatino for SOAP over JMS. Any pointers? Thanks... SOAP over JMS does makes sense a lot! Actually, within smaller network (as said in 1st reference), it makes a lot of sense to use JMS for reliable messaging. However, in bigger networks as HTTP is quite default and easy supported by servers (which might not be case by all servers), hence, jms-http-http-jms is no bad soln.

I’m looking for an example implementatino for SOAP over JMS. Any pointers?

Thanks…

]]> By: abeers http://www.subbu.org/blog/2005/03/soap-over-jms/comment-page-1#comment-35 abeers Thu, 23 Feb 2006 14:47:22 +0000 http://wp.subbu.org/2005/03/soap-over-jms/#comment-35 Subbu, "SOAP over JMS" indeed makes sense (at least to me and authors) and here is how.. JMS is not just an API or MDB - it's a messaging Service - simply put, a store and forward mechanism. You can send SOAP or any other text messages using the messaging service. Let's say application 'A' with a SOAP engine writes a SOAP request message into messaging service(queue) and application 'B' with a SOAP engine reads that SOAP message from the message service(queue), processes it and then responds in similar fashion - see there is no HTTP or SMTP used in this scenario, offcourse there are lower level protocols such as TCP/IP are involved. You are right in that JMS is not a protocol like HTTP or SMTP, but one can send SOAP messages bw apps using a JMS provider. Subbu,
“SOAP over JMS” indeed makes sense (at least to me and authors) and here is how..

JMS is not just an API or MDB – it’s a messaging Service – simply put, a store and forward mechanism. You can send SOAP or any other text messages using the messaging service.
Let’s say application ‘A’ with a SOAP engine writes a SOAP request message into messaging service(queue) and application ‘B’ with a SOAP engine reads that SOAP message from the message service(queue), processes it and then responds in similar fashion – see there is no HTTP or SMTP used in this scenario, offcourse there are lower level protocols such as TCP/IP are involved.

You are right in that JMS is not a protocol like HTTP or SMTP, but one can send SOAP messages bw apps using a JMS provider.

]]>