Hi Larry, Thank you! We've added all the classes we had in the CLASSPATH for 3.2.3 to the tomcat.bat classpath setting. We've tried to put them in lib/common but it didn't work (mainly the db2java.zip, jndi.jar and fscontext.jar). We also had to remove the jndi.properties from the db2java.zip, since it was in the way of our real jndi.properties.
However we are ok now, since we decided to go with 4.0.1 and the only thing we had to do was to handle the db2java.zip (renamed to jar, took out the jndi.properties - but right now is viewable from the common dir). So we didn't had to touch the bat any longer. It seems to be working fine. Best regards, Adrian Robitu e-Commerce Architect (416) 762-0032/410 IT.IP.IQ http://www.intelliware.ca -----Original Message----- From: Larry Isaacs [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 29, 2001 4:00 PM To: 'Tomcat Users List' Subject: RE: JNDI InitialContext not working when upgrading from Tomcat 3. 2.3 to 3.3 My first guess is that this would be a "classpath" issue. There is a big difference in classloader hierarchy between Tomcat 3.2.x and 3.3. Tomcat 3.2.x uses the CLASSPATH, Tomcat 3.3 doesn't. See: <http://jakarta.apache.org/tomcat/tomcat-3.3-doc/tomcat-ug.html#configuring_ classes> for more information. Were there jars or directories being added to the CLASSPATH for Tomcat 3.2.3? If so, how were they added to Tomcat 3.3? Cheers, Larry > -----Original Message----- > From: Adrian Robitu [mailto:[EMAIL PROTECTED]] > Sent: Thursday, November 29, 2001 12:49 PM > To: '[EMAIL PROTECTED]' > Subject: JNDI InitialContext not working when upgrading from Tomcat > 3.2.3 to 3.3 > > > Hi, > > We are in the process of migrating our app from 3.2.3 to 3.3 > (both on JDK > 1.2.2). The application uses a trim-down in-house EJB > container and Tomcat > as its servlet container. It works just fine under 3.2.3 but > not under 3.3. > Here is the sample code that we have problem with. > > Properties properties = new Properties(System.getProperties()); > InputStream input = > classLoader.getResourceAsStream("jndi.properties"); > ... > properties.load(input); > ... > Context context = InitialContext(properties); > VendorServiceHome home = (VendorServiceHome) > context.lookup(VendorServiceHome.class.getName()); > > Our jndi.properties file is: > > > java.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory > java.naming.provider.url=file\:d\:\\cellbucks > > After loading the properties we print them and get: > > {java.naming.factory.initial=com.sun.jndi.fscontext.RefFSConte > xtFactory, > java.naming.provider.url=file:d:\cellbucks} > which would indicate that jndi.properties is visible. > > Under 3.2.3 the context.lookup returns a > VendorServiceHomeImpl (which is > what we expect). Under 3.3 the context returns a > javax.naming.Reference. > > We've searched the archives, the manuals and other web > resources that we > could think of, but we didn't get anywhere. Any help on this > matter would be > highly appreciated. > > Best regards, > Adrian Robitu > e-Commerce Architect > (416) 762-0032/410 > IT.IP.IQ > http://www.intelliware.ca > > -- > 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]> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
