Cause found [was Re: How do I use a non-apache naming service with tomcat 4?]
Guys, I've isolated the cause of the problem down to the inclusion of the javax.naming package in my 'big everything' jar. If I remove the javax.naming package from the jar file, then all works well, if not, we get that wierd 'signature' problem with createNamingContext. (with or without enabling naming). Would it seem reasonable not to load naming support jars if tomcat isn't going to be running a [native] naming service? My problem here is I have a naming service I want to use and is packaged with the corresponding javax.naming package that it is based on the problem is that I'm unable (by default) to control what jndi stuff get's stuffed on the classpath of tomcat I'm unable to swap these (the naming support jars) around as tomcat's stuff seems to have been compiled against a different rev of the javax.naming stuff. So - Do you know what version of javax.naming is in tomcat 4's jndi.jar? I'm bundling the rev that came with j2ee 1.2.1 -Thom -- http://www.borland.com/newsgroups http://www.borland.com/devsupport/disclaim.html
Re: Cause found [was Re: How do I use a non-apache naming service with tomcat 4?]
Guys, I've isolated the cause of the problem down to the inclusion of the javax.naming package in my 'big everything' jar. If I remove the javax.naming package from the jar file, then all works well, if not, we get that wierd 'signature' problem with createNamingContext. (with or without enabling naming). Would it seem reasonable not to load naming support jars if tomcat isn't going to be running a [native] naming service? Which version of TC 4 are you using ? I believe the latest nightly builds could fix those problems. My problem here is I have a naming service I want to use and is packaged with the corresponding javax.naming package that it is based on the problem is that I'm unable (by default) to control what jndi stuff get's stuffed on the classpath of tomcat I'm unable to swap these (the naming support jars) around as tomcat's stuff seems to have been compiled against a different rev of the javax.naming stuff. So - Do you know what version of javax.naming is in tomcat 4's jndi.jar? It's the same as yours, but loaded by a different classloader, so it's not compatible anyway. Remy
Re: Cause found [was Re: How do I use a non-apache naming service with tomcat 4?]
Hi Remy, I'm running tomcat 4 beta 1. I'll download tonight's latest build and see how I fare with that. Thanks so much for the support! -Thom p.s. is there a b2 drop in the near future - I'm trying to focus my integration efforts on the nearest milestone build. Remy Maucherat wrote: Guys, I've isolated the cause of the problem down to the inclusion of the javax.naming package in my 'big everything' jar. If I remove the javax.naming package from the jar file, then all works well, if not, we get that wierd 'signature' problem with createNamingContext. (with or without enabling naming). Would it seem reasonable not to load naming support jars if tomcat isn't going to be running a [native] naming service? Which version of TC 4 are you using ? I believe the latest nightly builds could fix those problems. My problem here is I have a naming service I want to use and is packaged with the corresponding javax.naming package that it is based on the problem is that I'm unable (by default) to control what jndi stuff get's stuffed on the classpath of tomcat I'm unable to swap these (the naming support jars) around as tomcat's stuff seems to have been compiled against a different rev of the javax.naming stuff. So - Do you know what version of javax.naming is in tomcat 4's jndi.jar? It's the same as yours, but loaded by a different classloader, so it's not compatible anyway. Remy -- http://www.borland.com/newsgroups http://www.borland.com/devsupport/disclaim.html
