So with the current 3.2 branch code what do I do to produce the class loader problem?
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Remy Maucherat Sent: Wednesday, January 07, 2004 8:39 AM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] Web integration (clustering) updates Scott M Stark wrote: > The class loading is the same, the bigger recent change was a > refactoring No, your refactoring didn't break anything, as I did test it earlier. > of the embedded web service into the web container service and a deployer. > I would this is the source of the behavior change. What use case > produces the problem so I can look at it? For a variety of reasons, I needed to get a new class on shutdown of the service (a webapp deployer, to shutdown all the webapps). This is mostly to be consistent with Tomcat standalone, and it would actually be useful if using external contexts. So to fix it, I changed the setting so that a (useless) Host deployer would be created on startup: - <Host name="localhost" autoDeploy="false" deployOnStartup="false"> + <Host name="localhost"> -- xxxxxxxxxxxxxxxxxxxxxxxxxxxxx Rémy Maucherat Senior Developer & Consultant JBoss Group (Europe) SàRL xxxxxxxxxxxxxxxxxxxxxxxxxxxxx ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
