Not being able to use URLClassLoader seems like to big a restriction on integrated services. The web containers are too loosely integrated to be able to replace whatever class loader type they may be using with a JBoss specific one. Describe the change that was required in more detail. If a URLClassLoader delegates to the modified class loader as its parent does the change still work?
----- Original Message ----- From: "Andreas Schaefer" <[EMAIL PROTECTED]> To: "Rickard �berg" <[EMAIL PROTECTED]> Cc: "marc fleury" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Thursday, November 29, 2001 9:40 AM Subject: [JBoss-dev] URLClassLoader locking > Hi Geeks > > I finally could produce a URLClassLoader which can be close > therefore that the lock is released. This help us to inflate the deployed > file and overwrite the content instead of creating a copy after > the other. Unfortunately it does not seems that this can be done > under the cover but instead we have to replace the URLClassLoader > class by our own. > Now this is not a problem with JBoss but how is this working with > Tomcat, Jetty, Connectors etc. ? > > > xxxxxxxxxxxxxxxxx > Andreas Schaefer > Senior Consultant > JBoss Group, LLC > xxxxxxxxxxxxxxxxx > > > _______________________________________________ > 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
