|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Kevin Lewis
|Sent: Thursday, November 09, 2000 12:34 PM
|To: jBoss
|Subject: RE: [jBoss-User] Embedded Tomcat and Classloading
|
|
|
|> Is it supposed to be necessary to include your ejb-jar in
|> WEB-INF/lib when deploying .ear's into an embedded tomcat in jBoss?
|
|Well, it would be cool if that wasn't necessary, but at this point I
|don't see a way around it. If there was someone that understood Tomcat
|really well, we might be able to do something. I've tried, but it
|involves replacing the AdaptiveClassLoader. The problem is that JSPs
|often need app classes to compile.
how about putting everyone in WEB-INF/lib and telling jboss that is where he
should work, our deployer is flexible and will pick the stuff from that
library (ear) can tomcat deal with ear?
It is a bug of Tomcat design IMHO that the CL that compiles is the same that
is used in application layers... buaaaah! they
should talk less and code more.
I don't know... try it
marc
|> My understanding was that since it was in-VM, the classloader could
|> pick all of that up automatically. Using the latest jBoss from CVS
|> and Tomcat 3.2b6, it doesn't work that way. Also, calling new
|> InitialContext() from tomcat doesn't pick up the namingfactory,
|> etc.
|
|Put conf (or some place where the JNDI properties exist) in your class
|path.
|
|-Jason
|
|
|--
|--------------------------------------------------------------
|To subscribe: [EMAIL PROTECTED]
|To unsubscribe: [EMAIL PROTECTED]
|Problems?: [EMAIL PROTECTED]
|
|
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
