Comments on: Using a JMS Provider with MDBs via the J2EE Connector Architecture http://almaer.com/blog/using-a-jms-provider-with-mdbs-via-the-j2ee-connector-architecture blogging about life, the universe, and everything tech Sat, 08 Sep 2012 07:06:53 -0700 http://wordpress.org/?v=2.8.4 hourly 1 By: James Strachan http://almaer.com/blog/using-a-jms-provider-with-mdbs-via-the-j2ee-connector-architecture/comment-page-1#comment-4161 James Strachan Thu, 24 Jun 2004 20:03:04 +0000 http://almaer.com/blog2/using-a-jms-provider-with-mdbs-via-the-j2ee-connector-architecture#comment-4161 Agreed! With the Queue* and Topic* APIs JMS 1.0.2b was a little painful to use. Now JMS 1.1 is much nicer, now its finally got a polymorphic API across Queues and Topics! And thanks to JCA we don't have to struggle with J2EE container specific ways to configure different JMS providers. We can all just use RARs. From a purely selfish perpsective, this also means if you work on an open source JMS 1.1 provider (hint hint: http://activemq.codehaus.org/ :), you've much less work to do to integrate it into any J2EE 1.4 container :) Agreed! With the Queue* and Topic* APIs JMS 1.0.2b was a little painful to use. Now JMS 1.1 is much nicer, now its finally got a polymorphic API across Queues and Topics!

And thanks to JCA we don’t have to struggle with J2EE container specific ways to configure different JMS providers. We can all just use RARs.

From a purely selfish perpsective, this also means if you work on an open source JMS 1.1 provider (hint hint: http://activemq.codehaus.org/ :), you’ve much less work to do to integrate it into any J2EE 1.4 container :)

]]>