[ http://issues.apache.org/jira/browse/GERONIMO-791?page=all ] Dain Sundstrom closed GERONIMO-791: -----------------------------------
Fix Version: 1.0-M5 Resolution: Fixed Deleting modules/kernel/src/java/org/apache/geronimo/gbean/GBeanLifecycleController.java Sending modules/kernel/src/java/org/apache/geronimo/gbean/runtime/GBeanInstance.java Sending modules/kernel/src/java/org/apache/geronimo/gbean/runtime/GBeanInstanceState.java Sending modules/kernel/src/test/org/apache/geronimo/kernel/GBeanTest.java Sending modules/kernel/src/test/org/apache/geronimo/kernel/MockEndpoint.java Sending modules/kernel/src/test/org/apache/geronimo/kernel/MockGBean.java Transmitting file data ..... Committed revision 225470. > Remove GBeanInstance support for J2EEManagedObject methods > ---------------------------------------------------------- > > Key: GERONIMO-791 > URL: http://issues.apache.org/jira/browse/GERONIMO-791 > Project: Geronimo > Type: Bug > Components: kernel > Versions: 1.0-M3 > Reporter: Aaron Mulder > Assignee: Dain Sundstrom > Fix For: 1.0-M5 > > The current "GBean Framework" provides support for the methods of > J2EEManagedObject, meaning they're effectively implemented for every GBean > regardless of whether the GBean itself implements them. This happens in > GBeanInstace.addManagedObjectAttributes, and the attributes in question are: > objectName (String, "special") > stateManageable (boolean, "framework") > statisticsProvider (boolean, "framework") > eventProvider (boolean, "framework") > These should be removed. If a GBean wants to implement J2EEManagedObject, it > should provide its own implementation of this stuff. (It can get its > ObjectName injected as a magic attribute.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira