Arshad Mahmood wrote:
> Hmm, I will investigate further. It seemed to be that "ResourceLink" in the
> server.xml
> "<Context" entry was going into a naming context with name
> "//Standard/myapp" but
> the one which I retrieved from the servlet was called
> "//Standard/localhost/webapp". I will
> debug this further.

The context name is not important for the global context. The 
ResourceLink are actually yet another reference which is bound into the 
webapp naming context, and use a standard JNDI object factory 
(factory.ResourceLinkFactory). The lookup in the actual global context 
then just uses a static reference instead of another lookup.

> I will have a look at the JNDI example servlet. I must confess I was using
> the
> JNDI-Howto in the docs.

Which may not be totally accurate, and don't talk at all about how it 
actually works.

> The latest version of 4.1 from CVS (although it's a little broken because
> MBeanUtils
> does't compile, but I am not using that anyway).

Really ? It does build for me. What's the problem ?
I do get an exception on shutdown, or when removing a context, though.

> Thanks for your help. I will try and pin the problem down a bit more.

Sounds good.

Remy


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to