Yeah that's one way, I mean the class visibility is really what we want, so
we can have sars reference ears and what not, should be real good. So
class.forName() barfs in the case of web-inf/classes? ah fuck
class.forName()
I mean it...
Brain: Now, Pinky, if by any chance you are captured
during this mission, remember you are Gunther
Heindriksen from Appenzell. You moved to
Grindelwald to drive the cog train to Murren.
Can you repeat that?
Pinky: Mmmm, no, Brain, don't think I can.
-- Where Rodents Dare
LOL, that might get me to sleep finally, 5AM reading pinky, meeting at 11AM
:)
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Scott
|M Stark
|Sent: Thursday, February 21, 2002 2:00 AM
|To: [EMAIL PROTECTED]
|Subject: Re: [JBoss-dev] Why add anything from a war to the JBoss
|classpath
|
|
|We don't really have to choose an all or nothing model anyway.
|Make it a property of the deployer whether or not it wants
|the MainDeployer to handle subdeployments of elements found
|inside of its deployment package. The Jetty can say yes,
|the Tomcat can say no.
|
|xxxxxxxxxxxxxxxxxxxxxxxx
|Scott Stark
|Chief Technology Officer
|JBoss Group, LLC
|xxxxxxxxxxxxxxxxxxxxxxxx
|
|
|
|_______________________________________________
|Jboss-development mailing list
|[EMAIL PROTECTED]
|https://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development