From: John L. <joh...@ep...> - 2002-03-13 15:48:28
|
I have been porting to JBoss3.0beta and have run into a problem that seems to be related to classloading. So I wanted to get some verification that I have things setup correctly. This stuff all works fine on JBoss2.4 I have a JMX MBean that creates threads that act as clients. I have all the jars that my mbean needs in lib/ext I created a my-service.xml file in deploy directory with a classpath of <classpath codebase="lib/ext" archives="*"/> This loads my mbeans fine. My problem is that my service has background threads that wake up and try to do some work. On thing is they run jython scripts. The jython interpreter dies trying to import classes from my jars. Yet in order for the jython to be fired it must have seen these classes. My guess is that the way jython loads classes is not compatiable with JBoss class loaders. Jython site says thay don't load classes using a thread classloader and have a task to improve this. Any workarounds with JBoss3.0 I wouldn't normally ask for any ideas but this did work fine in JBoss2.4 and I don't have that much documentation on 3.0 about how the new service loading works. I will say that the new design is well layed out. Having dependency is a real plus. Thanks, jcl. |