Hi Geeks As you maybe know JSR-77 defines a vendor-neutral way to manage J2EE application server. JSR-77 works like JMX except that it uses only a few data types (basic data types, String and Stats (statistic data containers)). The rest are links to other managed objects. Thus you can navigate through the app. server following the links until you get the information you need (something like when you surf through the net).
Right now the MEJB (mantatory EJB to enable a JSR-77 client to access and work with the app. server) is available but empty. Therefore I would suggest the following implementation of the JSR-77 spec.: - MEJB maps JSR-77 "links" to the JSR-77 MBeans - JSR-77 MBeans are the bridge between JSR-77 spec. and the JBoss implementation - JSR-77 MBean represents a "ManagedObject" which make the mapping JSR-77 <--> JBoss pretty easy - Each JBoss service is reponsible to create the appropriate JSR-77 MBeans and to provide the information to link it with its parents whereas the JSR-77 MBean know how to create the links I dropped the idea of a controller getting the information from the services and creating the JSR-77 MBeans. The service MBean has the appropriate knowledge to create the JSR-77 MBean and thus make the controller superfluous. As time permits I will start make the first implementation to show what this means code-wise. Feedback ? xxxxxxxxxxxxxxxxx Andreas Schaefer Senior Consultant JBoss Group, LLC xxxxxxxxxxxxxxxxx _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
