That's certainly cleaner, both in terms of implementation and in clarity for a user
looking at the config file.
As for handling mbeans, options in ascending order of effort are:
1) Continue to support the current mechanism where
org.jboss.system.microcontainer.ConfigureAction calls into the binding manager. Clunky but
supports existing end-user custom mbean services with no change on their end required.
2) Convert mbeans services with ports to pojos w/ @JMX. For our own services, a good
thing to do anyway in most if not all cases.
3) Add support for value-factory to the JMX config. Not sure what that entails.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167596#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...