[ http://jira.jboss.com/jira/browse/JBJMX-89?page=comments#action_12316545 ] Michael Kopp commented on JBJMX-89: -----------------------------------
You are both right. The MBean I am talkig about is not part of a sar or -service.xml, but is registered by one of my components during startup. As such it can and is a private class. But as Adrian pointed out, the server should access the interface and not the implementation, thus it should not be a problem. unfortuantelly the mbean server is accessing the implementation. > Access the interface not the implementation > ------------------------------------------- > > Key: JBJMX-89 > URL: http://jira.jboss.com/jira/browse/JBJMX-89 > Project: JBoss JMX > Type: Bug > Versions: JBossAS-4.0.1 > Reporter: Michael Kopp > Assignee: Dimitris Andreadis > > > I have a package private MBean class, the StandardMBean interface is public > though! > class WorkManager implements WorkManagerMBean > WorkManager is private > WorkManagerMBean is public > Unfortunatelly jboss jmx accesses the implementation directly, thus throwing > an IllegalAccessException. If it would access the mbean via the provided > interface this would not happen. (like jdk 5 is doing) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira ------------------------------------------------------- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
