Hmm. True.. Here is what I was referring to: Pg 37 from the 1.0 JMX instrumentation spec:
"The name of an MBean's Java interface is formed by adding the MBean suffix to the MBean's Java class name. For example, the Java class MyClass would implement the MyClassMBean interface. The interface of a standard MBean is referred to as its MBean interface." Although not explicitly stated, I think it could be inferred, since there is not way per the spec to identify the location of the interface or impl from one another (via a manifest entry or something). I know that JB and WLS both assume the same package by default. But alas, I'm not sure if Jboss provides a means to declare this or not. Nothing stands out in the pay-for docs to me.. AFAICT, it appears that the code="" attribute in your -service.xml is all that is used to find the rest of the mbean. HTH, James -----Original Message----- From: Greg Turner [mailto:gturner@;tiburon-e-systems.com] Sent: Monday, November 04, 2002 11:40 AM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] MBean Question Thanks James, I skimmed the spec and could not find any specs on the package of the interface. Furthermore, the manual from the adanced JBoss training has a diagram of a sar file that shows the MBean and its interface as being in different packages. Scott or Juha want to weigh in here ? Greg James Higginbotham wrote: >I believe the mbean spec from Sun requires the interface and impl to be >in the same package, with a specific naming convention. Check the spec >for details.. > >James > >-----Original Message----- >From: Greg Turner [mailto:gturner@;tiburon-e-systems.com] >Sent: Monday, November 04, 2002 10:21 AM >To: [EMAIL PROTECTED] >Subject: [JBoss-user] MBean Question > > >I have an MBean which I deploy as a sar file with no problems provided >I > >put the MBean class and its interface in the same package. However, if >I move the interface into a separate package, and taking care that the >MBean class and interface are in the sar file, JBoss throws an >exception, complaining that my class does not expose an MBean interface. > > I'm running JBoss 3.2 on Win2000. Is this a bug, or is there > something > >else that needs to be put into the deployment descriptor to ensure that >the interface is recognized ? > >Thanks > >Greg > > > >------------------------------------------------------- >This SF.net email is sponsored by: ApacheCon, November 18-21 in Las >Vegas (supported by COMDEX), the only Apache event to be fully >supported by the ASF. http://www.apachecon.com >_______________________________________________ >JBoss-user mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/jboss-user > > >------------------------------------------------------- >This SF.net email is sponsored by: ApacheCon, November 18-21 in Las >Vegas (supported by COMDEX), the only Apache event to be fully >supported by the ASF. http://www.apachecon.com >_______________________________________________ >JBoss-user mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/jboss-user > > > > -- Greg Turner, JBoss Authorized Consultant Tiburon Enterprise Systems http://www.tiburon-e-systems.com Box 1171 Tiburon, CA 94920 415-927-2543 ------------------------------------------------------- This SF.net email is sponsored by: ApacheCon, November 18-21 in Las Vegas (supported by COMDEX), the only Apache event to be fully supported by the ASF. http://www.apachecon.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ------------------------------------------------------- This SF.net email is sponsored by: ApacheCon, November 18-21 in Las Vegas (supported by COMDEX), the only Apache event to be fully supported by the ASF. http://www.apachecon.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
