> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Rickard �berg
> Sent: Tuesday, May 23, 2000 11:23 PM
> To: jBoss Developer
> Subject: Re: [jBoss-Dev] A little more confused
>
>
> marc fleury wrote:
> > > But then we'd have to introduce a threadlocal to hold it. The
> point was
> > > that since we associate the thread with a classloader, why
> not reuse it
> > > for the java: namespace. But sure, we could "go back" to synchronized
> > > threadlocals ;-)
> > >
> >
> > Still, why storing it as a reference in the class loader??? that is the
> > question.
>
> It is something that is associated with a thread. It is something that
> doesn't change. The question is: why not???
>
<morning>
it's clearer, yes I remember the discussion on the ClassLoader thread now.
Sorry, never mind.
> > I understand it's usage (I asked for a non-thread loco construct in
> > *run-time* , as you point out ;) but why storing it there in between
> > invocations ..
>
> Because it doesn't change. Each container has its own BeanClassLoader,
> and the java: namespace is immutable for each container.
>
> > Have you created a new JNP in there? one that is not Thread
> local but works
> > directly from the thread? that would be great, but geez let us
> know (is that
> > what you did?, that would be really cool)
>
> org.jboss.naming.java.javaURLContextFactory.
>
> Yes.
I remember now... never mind
marc
>
> > > > > > 4- Since your interceptors are "newed" for container
> > > > > interceptors at this
> > > > > > point you should use the set, and then 3 applies
> > > >
> > > > Well setting the container on all those interceptor mean that
> > > they are not
> > > > shared just belong to one... that is something we might
> > > "reverse". It makes
> > > > sense... bean should be the only place unless you can justify the
> > > > "necessity" for BeanCLassLoader JNDI root as opposed to just
> > > using the bean
> > > > metadata... if you ask me it is because you use your EJX stuff
> > > and you don't
> > > > have a "storeRoot" ;-) never mind.
> > >
> > > I don't understand. The reason for the BeanClassLoader is to have
> > > something associated with the executing thread from which we
> can get the
> > > JNDI root. The metadata isn't associated with a thread, so we
> can't use
> > > that.
> > >
> >
> > Maybe the reason we are not on the same wave is that you use
> this (retrieve
> > information from it) only in JNP, and not at all in the
> container plugins..
> > is that the real reason?
>
> Correct.
>
> /Rickard
>
> --
> Rickard �berg
>
> @home: +46 13 177937
> Email: [EMAIL PROTECTED]
> http://www.telkel.com
> http://www.jboss.org
> http://www.dreambean.com
>
>
