Hi Scott > A problem that keeps popping up with the JSR77 integration > is that it is rather invasive and if it fails it breaks existing code. > A better integration path would be strictly as external listeners > to JMX events. This would clean up the integration, make it easy > to disable and require that key events were being made available > for purposes other than JSR77.
I don't think this is possible. We are already listening to JMX events to determine the state of a component. But this is only the easy part of JSR-77. Even thought that JSR-77 spec. does not really cover what it was supposed to do the main part currenlty is to retrieve and calculate performance statstics. The rest is just to provide a JSR-77 compliant view to an application server. BTW I am not aware that JSR-77 breaks existing code. Mostely it was the other way around that changes where made and the JSR-77 stuff was left out and broke. The design is made that the invasive part is as small as possible. So what is the source of the problem ? Have fun - Andy _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
