Alright. Fair enough. I can understand that--JNDI uses a different class
loader than Tomcat (or something), so that it can't see new classes that are
available to the Tomcat class loader (I guess).
So what happens if you run JBoss & Tomcat in the same JVM? What happens if
you use a common classloader instead of separate class loaders? It seems
like, based upon my logic above, the common classloader should work, and
perhaps separate class loaders will work. Is this the case? I really don't
want to restart Tomcat every time I make a change to my EJBs.
Thanks!
-dan
On Thursday 08 February 2001 16:32, you wrote:
> > (A lot of stuff about my classpath problems with Tomcat & JBoss)
>
> There have been a lot of discussions on this list around this - and the
> general consensus is that it doesn't work as it should (although I've
> noticed an email on another list - turbine - that highlights a bug they've
> found in Catalina/tomcat4 to do with classloaders - so hopefully this will
> fix it).
>
> The way I get it to work is to put all my applications jars (I have no code
> outside of jars) including the jndi.properties onto the system classpath
> before starting tomcat.
>
> HTH,
> Chris
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
