I assume you noticed in the documentation that Tomcat 3.3 startup scripts ignore your CLASSPATH. Did you modify the tomcat.bat/tomcat.sh file to include the jndi.properties file? If so, what is the error you are seeing?
Cheers, Larry > -----Original Message----- > From: Mike Comb [mailto:[EMAIL PROTECTED]] > Sent: Thursday, December 06, 2001 10:37 PM > To: [EMAIL PROTECTED] > Subject: RMI/JNDI problem w/tomcat 3.3 > > > Hi, I am trying to upgrade from tomcat 3.2.3 to 3.3 and I am having a > problem. Under 3.2.3 I was able to get tomcat to act as a > JNDI server by > adding a jndi.properties file to my classpath with the > following contents... > > ------------ > java.naming.factory.initial=com.sun.jndi.rmi.registry.Registry > ContextFactory > java.naming.provider.url=rmi://localhost:1099 > ------------ > > an RMI server was automatically started on port 1099 as part > of the tomcat > process. With TC 3.3 this no longer works. I found a couple > of old emails > mentioning that tc3.3 may not be able to open that file, but no real > details. Can someone please tell me what is going on and if > there is any > work around? > > Thanks, > -Mike > > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
