|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?
that won't actually since the CL is the ACL in one case the jboss UCL in the
other, never mind...
man the compilation and app stuff must REALLY be seperated that is a tomcat
bug
marc
|
|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]
|
|
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
