Traditional JMS-based MOM
provides ways to address the above concerns, which we can leverage even in normal
web services. It is in this context that we need to look into combining the MOM
infrastructure with SOAP (Web Services), to get the best of both the worlds.
SOAP over HTTP versus SOAP over JMS
SOAP is transport independent and can be bound to any transport. The usual
transport binding for SOAP is HTTP and SOAP over HTTP is what we usually look
at as interoperable. HTTP belongs to the application layer of both the Open System
Interface (OSI) model (layer 7) and the Internet Protocol (IP) suite (layer 4 or 5).
The following WSDL snippet shows what for a HTTP bound SOAP message
looks like:
type="impl:IHelloWeb">
??? ??? ???
Access Web Services Using the JMS Channel
[ 202 ]
transport="http://schemas.xmlsoap.org
/soap/http"/>
name="HelloWebService">
Due to the many QOS features of JMS, SOAP over JMS offers more reliable and
scalable messaging support than SOAP over HTTP.
Pages:
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286