This is because JMS is not an "over-the-wire" protocol.
Instead, JMS is a Java API which requires a client to use a JMS provider library (a jar
file) provided by the vendor of the JMS service provider. This is analogous to requiring
a JDBC driver similar to classes12.jar from Oracle for connecting to an Oracle
server from a java application. The actual "over-the-wire" protocol to be used under
Chapter 11
[ 203 ]
the covers within the JMS provider library is not defined and is left open for vendors to
have their own implementations. The interoperability is not easy even if we consider
the java world alone. That is, if we have an IBM Websphere JMS provider and a client
program from within the BEA Weblogic application server need to access the JMS
server. Even though both the platforms are java-based, the integration might not be
straightforward due to the JMS implementation clashes. Moreover, JMS being an API
doesn't ask vendors to implement any additional services and doesn't standardize
the data structure exchanged. However, JMS still is a viable mechanism to MOM that
enables web services.
Pages:
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288