Bugs item #608837, was opened at 2002-09-13 10:41 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=608837&group_id=22866
Category: JBossMX Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Alasdair MacLeod (macleoa) Assigned to: Nobody/Anonymous (nobody) Summary: Can't deploy default-package MBean Initial Comment: Windows2000 Professional java -version java version "1.4.0" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92 Java HotSpot(TM) Client VM (build 1.4.0-b92, mixed mode) Jboss3_0_2 pulled from CVS. Couldn't get console traces but include server.log instead. Log messages with AML are my additions. It seems you can't deploy (via user-service.xml) an MBean if it's package is the default package. The org.jboss.system.ServiceCreator reports it cannot find the class even though it seems to have found the jar ok. E.g. public class Ali implements AliMBean {...} cannot be deployed but will deploy once moved to package a.b.c; I include the user-service.xml and log files for each scenario. It looks like the classloader is throwing an exception when loadClass() is called. Haven't had time to pursue it further but will try if someone points me in the right direction (I don't know anything about the JBoss classloader framework). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=608837&group_id=22866 ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development