> Is any of them an AdaptiveClassloader? During the request it 
> definitely
> should be. They might have forgotten it during init.

If I reposition my context interceptor (the thing that reads the
mappings), I can get an adaptive class loader from the context.

> Aren't you able to access the classloader for the app somehow? If so
> then set it before doing the bindings.

Right.  I can get it indirectly from the initialization context.

> The JNP you are using is not remote. It is purely local (i.e. 
> "java:" is
> local). However, the stuff you bind in there could be remote, i.e. the
> EJB home.

Okay.

> You should be fine if you can make sure that the context 
> classloader is
> set properly before you make your bindings.

The problem now is that it tells me that comp is not bound when I do new
InitialContext().lookup("java:comp"):

[EmbeddedTomcat] javax.naming.NameNotFoundException: comp not bound

I can create that, too (which I did to no avail), but I'm guessing
there's something else wrong.

Here's what I get if I create both comp and env:

[EmbeddedTomcat] javax.naming.NameNotFoundException: env not bound
[EmbeddedTomcat]        at
org.jnp.server.NamingServer.getBinding(NamingServer.java:420)
[EmbeddedTomcat]        at
org.jnp.server.NamingServer.getBinding(NamingServer.java:428)
[EmbeddedTomcat]        at
org.jnp.server.NamingServer.getObject(NamingServer.java:434)

Reply via email to