You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by "T. Park" <tp...@borland.com> on 2001/03/27 06:09:19 UTC
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
Re: Cause found [was Re: How do I use a non-apache naming servicewith
tomcat 4?]
Posted by "Craig R. McClanahan" <cr...@apache.org>.
On Tue, 27 Mar 2001, T. Park wrote:
> Craig,Remy,
>
> downloading the latest nightly build resolved my problem... thanks!
>
Cool.
>
> ...but only after I dropped that 'big everything' jar into the common/lib
> folder.
>
> So there seems to be a chicken & egg thing regarding what order certain
> components need to be in
> for the new tomcat to play with an alternative naming service.
>
> My InstanceListener class goes into server/lib just fine, but the support
> class (I.e. the one containing javax.naming) needs
> to go in the common area.
>
> Can you tell me why this would be? I know it's something to do with the new
> classloading scheme
> but I can't see why it would matter.
>
The reason something would need to be in "common" is if it needs to be
visible to both the Catalina classloader and a webapp class loader. If
you consult the classloaders.html doc for Catalina, you will see that
this is the only configurable place that these two hierarchies meet. It
sounds like there must be things in your "big everything" JAR that meet
that description.
> -Thom
>
Craig
Re: Cause found [was Re: How do I use a non-apache naming servicewith
tomcat 4?]
Posted by "T. Park" <tp...@borland.com>.
Craig,Remy,
downloading the latest nightly build resolved my problem... thanks!
...but only after I dropped that 'big everything' jar into the common/lib
folder.
So there seems to be a chicken & egg thing regarding what order certain
components need to be in
for the new tomcat to play with an alternative naming service.
My InstanceListener class goes into server/lib just fine, but the support
class (I.e. the one containing javax.naming) needs
to go in the common area.
Can you tell me why this would be? I know it's something to do with the new
classloading scheme
but I can't see why it would matter.
-Thom
"Craig R. McClanahan" wrote:
> On Mon, 26 Mar 2001, T. Park wrote:
>
> > 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.
> >
>
> There will be soon, but I've been notified that someone is working on a
> "real" patch for the sealing violation problems under JDK 1.3 JVMs. I'd
> like to give him a chance to finish before cutting beta 2.
>
> Since I'm going to be at O'Reilly Java Conference for the remainder of
> this week (I'm speaking at 4:15 on Thursday about Web Application
> Architectures), the earliest possible time for a beta 2 release will be
> this weekend.
>
> In the mean time, working with a recent nightly build will save you the
> time it takes to deal with issues that have already been fixed (and there
> have been around 200 CVS commits on Tomcat 4.0 since beta 1).
>
> Craig
--
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?]
Posted by "Craig R. McClanahan" <cr...@apache.org>.
On Mon, 26 Mar 2001, T. Park wrote:
> 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.
>
There will be soon, but I've been notified that someone is working on a
"real" patch for the sealing violation problems under JDK 1.3 JVMs. I'd
like to give him a chance to finish before cutting beta 2.
Since I'm going to be at O'Reilly Java Conference for the remainder of
this week (I'm speaking at 4:15 on Thursday about Web Application
Architectures), the earliest possible time for a beta 2 release will be
this weekend.
In the mean time, working with a recent nightly build will save you the
time it takes to deal with issues that have already been fixed (and there
have been around 200 CVS commits on Tomcat 4.0 since beta 1).
Craig