Re: Context.INITIAL_CONTEXT_FACTORY

2007-02-02 Thread Pid
supply an IBM JNDI Factory Class named "com.ibm.websphere.naming.WsnInitialContextFactory" as the "Context.INITIAL_CONTEXT_FACTORY". We can then find our driver and all is well. Clearly, in Tomcat the above mentioned class does not exist. I've been all over the place trying to find an equivalent

Re: Context.INITIAL_CONTEXT_FACTORY

2007-02-02 Thread Fran Varin
g to utilize Tomcat for testing purposes). In > WebSphere we can supply an IBM JNDI Factory Class named > "com.ibm.websphere.naming.WsnInitialContextFactory" as the > "Context.INITIAL_CONTEXT_FACTORY". We can then find our driver and all is > well. > > Clea

Re: Context.INITIAL_CONTEXT_FACTORY

2007-02-02 Thread Pid
Fran Varin wrote: Well, let me see if I can paint an accurate picture...The application as it is currently running in WAS uses a properties file to externalize everything we need to connect to a datasource. The code itself will add the initial context class name to the properties file that is han

Re: Context.INITIAL_CONTEXT_FACTORY

2007-02-01 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Fran, Fran Varin wrote: > The code itself will add the initial context class name to the > properties file that is handed to javax.naming.initialcontext at the > time the context object is constructed. Can you post your code? I have never tried to sp

Re: Context.INITIAL_CONTEXT_FACTORY

2007-02-01 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Fran, Fran Varin wrote: > On the one hand > it "appears" that you can modify the server.xml file (which we have done) > and the the datasource and context will be defined globally. We tried > that...same error. Here is exactly what I have in my setu

RE: Context.INITIAL_CONTEXT_FACTORY

2007-02-01 Thread Fran Varin
s strictly prohibited. If you have > received this communication in error, please notify us > immediately by replying to this e-mail. > > > > - > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For a

Re: Context.INITIAL_CONTEXT_FACTORY

2007-02-01 Thread Fran Varin
ng under >> WebSphere (We are trying to utilize Tomcat for testing purposes). In >> WebSphere we can supply an IBM JNDI Factory Class named >> "com.ibm.websphere.naming.WsnInitialContextFactory" as the >> "Context.INITIAL_CONTEXT_FACTORY". We can then find

RE: Context.INITIAL_CONTEXT_FACTORY

2007-02-01 Thread Nelson, Tracy M.
| From: Fran Varin [mailto:[EMAIL PROTECTED] | Sent: Thursday, 01 February, 2007 08:05 | | It boils down to my attempt at using | "org.apache.naming.java.javaURLContextFactory". However, when I do I | receive "javax.naming.NameNotFoundException: Name jdbc is not bound | in this Context:". Are yo

Re: Context.INITIAL_CONTEXT_FACTORY

2007-02-01 Thread Pid
"com.ibm.websphere.naming.WsnInitialContextFactory" as the "Context.INITIAL_CONTEXT_FACTORY". We can then find our driver and all is well. Clearly, in Tomcat the above mentioned class does not exist. I've been all over the place trying to find an equivalent class that is

Context.INITIAL_CONTEXT_FACTORY

2007-02-01 Thread Fran Varin
"com.ibm.websphere.naming.WsnInitialContextFactory" as the "Context.INITIAL_CONTEXT_FACTORY". We can then find our driver and all is well. Clearly, in Tomcat the above mentioned class does not exist. I've been all over the place trying to find an equivalent class that is part of Tomcat. It