> Afaik no, the ACL from tomcat picks them up... aaaaaahhhh!!!!!!!!
>
> but now that I think about it... could that be the trick?
I think it is. I see it as a two-fold problem:
1. The JSPs need the classes to compile, and Tomcat does this through
the AdaptiveClassLoader.
2. Web-tier apps need to lookup classes. The web classes are loaded by
the ACL. JNDI uses the thread context class loader (boom! class cast).
> I mean that the ACL picks up the classes and says "yes I know
> how to resolve
> it" and the URLCL picks for jBoss/JNDI and the VM says "nope"
> not the same.
>
> hmmmm if your ACL resolves the stuff that could be it, the CL are well
> installed it is just that someone down the hierarchy yells
> "yes, I know that
> class" when it should be up...
This is the case.
> could be? can you resolve the CL in a System.out???
Already resolved. I traced it in and the app classes are being loaded
by the ACL, while JNDI is using the thread context class loader.
Thanks for the explanation on class loaders. I agree that it's a big
issue (I've been living it with this embedded tomcat work).
-Kevin Lewis
