On Sat, 10 Mar 2001, David Wall wrote:
> ACK, now that I've solved the JCE provider problem, the next one to rear
> itself is JNDI and JMS.
>
> With JMS, you use the JNDI InitialContext object that includes the class
> name of the provider of the JMS. Then, JNDI uses that to instantiate the
> class and create the initial connection for JNDI queries.
>
> Do you have any idea how to work with this in a Tomcat world? I'm not sure
> how to cause this to load since I think it's that nasty situation in which a
> lower-level classloader doesn't know how to move up. In this case, do you
> think it's "okay" to put the JMS classes in the CLASSPATH for Tomcat? I've
> seen that it will work.
>
> Will there be a problem next with JDBC, in which the JDBC driver is also
> dynamically created? Perhaps that will be okay, though, since the driver is
> loaded by my code rather than something like JNDI.
>
Tomcat 4.0 already includes a JNDI implementation, and includes object
factories for <env-entry> and <resource-ref> values from web.xml. You can
also define your own object factories for object types not supported by
default.
> David
>
>
Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
