Head's up on JMS provider specific JNDI access.

[David Chappell <ch...@sonicsoftware.com>]

Hi all,
I'm a couple of hours away from providing documentation on how to set up
the JMS transport layer and run the JMS sample.  This includes a section
for vendor specific setup of a JNDI store, and ConnectionFactory, Topic,
and Queue destinations.  I can provide instructions for SonicMQ, but
that's the extent of where I can go with that.  I'm looking to other's
who are familiar with other JMS providers to provide the appropriate
information.

We are assuming the use of Sun's FSContext file-based JNDI provider for
use by the sample.  The minumum that needs to be documented is how to
set up a JMS provider specific ConnectionFactory with a JNDI name of
"MyCF", and how to set up a Queue destination with a JNDI name of
"MyQ".  If the JMS Provider comes with a out-of-the-box sample queue
already set up that "MyQ" can be pointed at, then there is no need to
further explain how to use the JMS provider-specific admin tool to
create a Queue.

Sorry about the last minute-ness of this, but it just sort-of dawned on
me that this cross-provider piece was necessary as I am going through
this.  This is of course optional, but I don't really want this to come
across as a Sonic-only kind of thing.  Its designed to be open and
vendor-neutral.  Any help will be appreciated.
Dave

-- 
Sonic Software - Backbone of the Extended Enterprise
--
David Chappell <ch...@sonicsoftware.com> Office: (781)999-7099
Mobile: (617)510-6566
Vice President and Chief Technology Evangelist, Sonic Software
co-author,"Java Web Services", (O'Reilly 2002)
"The Java Message Service", (O'Reilly 2000)
"Professional ebXML Foundations", (Wrox 2001)
--