"[EMAIL PROTECTED]" wrote : "[EMAIL PROTECTED]" wrote : guys, don't we have better doc for people wanting to try something like this? | | What makes you think I would document people creating their own classloaders? | (I will but this stuff will be in the reference guide rather than the user guide). | JavaEE says its illegal for an application to create a classloader. | | The approach described won't even work with OSGi style classloading. | The method works because currently things are using the "big ball of mud" | classloading policies. | | The correct way is to modify the classpath of a deployment using | one of the methods Ales showed. | Which is actually deployer docs rather than classloader docs. ;-)
Thanks for you help Adrian. Regarding the "correct way", we receive the deployable unit jars via JMX, then unpack and process it, do you mean we should go for a MC deployer for it, and also for classes generated? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188794#4188794 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4188794 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user