The Tomcat fixes don't seem to help me at all.  I have the same problems
I had before.  Here's a summary:

1.  If I use things as they are (with respect to the JNDI interceptor
and Jdk12 interceptor), when I do a JNDI lookup, I get a
NameNotFoundException: env not bound.  That tells me I'm not getting
back the same context class loader as was used to initialize the
application and build the JNDI.

2.  If I remove the Jdk12Interceptor, the JNDI environment is there, but
I get a class cast exception on the object returned from the JNDI
lookup, because the class looking up the object was loaded by a
different class loader than the object returned.  (If I remove eth JNDI
interceptor and include the Jdk12Interceptor, I have the same problem as
in #1.)

3.  If I remove the domain classes from the war (only put them in the
jar), the JSPs won't compile because the JSP compiler doesn't use the
context class loader that's hooked into jBoss to load classes.

If I'm doing something wrong, here, I'd be happy to fix it to get this
stuff to work.  We're still on PRE-PROD-04 because it's the only one
where the Tomcat integration worked (even if it was by luck ;-).

-Kevin Lewis

Reply via email to