> -----Original Message-----
> From: David Chappell [mailto:[EMAIL PROTECTED]]
> 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".
My suggestion would be to leave this completely out of the documentation. No Sonic,
no MQSeries, no OpenJMS, no SwiftMQ, no Fiorano, no SpiritSoft, no AshnaMQ, no SunONE,
no OracleAQ, no JBossMQ... It's a slippery slope to start covering
implementation/configuration details for specific products and versions, since you
more or less have to let everyone come to the party in the interest of fairness and
because some of the details can get hairy. (There is at least one version of one
product on my list above where satisfying your basic requirement of QCF and Q in JNDI
would require actually writing proxy classes and providing a good amount of
documentation...)
Asking a JMS vendor to provide a way to make relevant objects accessible through JNDI
is not a big deal -- I can't think of any serious vendor who doesn't -- and I can
think of where to find it in the documentation in most cases.
Just $0.02.
-- Paul
