List-
I've written an mbean which is the last mbean started by JBossMX. This means that my application has deployed, prior to starting the mbean. My MBean uses the jakarta digester utility to digest an xml file. The way the digester implementation works is you create rules which dynamically instantiate classes. Now- starting my mbean works fine as long as my digester lib is present in lib/ext. My problem occurs when my logging into my application, where the digester is used by an EJB to digest another XML file. Because the digester was loaded in the (root?) classloader, it does not have access to the classes within my (application?) classloader, so the digest process fails from the EJB. My question is- how does one: a- force jboss to obtain the digester classes from my application classloader, or b- force my mbean to use a digester instance which is loaded by a classloader which is NOT a parent of my application classloader (thus forcing the application classloader to load the class) thanks! jstiefel ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
