"flavia.rainone(a)jboss.com" wrote : | Should the migration tool generate a beans.xml file that declares every MBean just as a POJO, without injecting the @JMX annotation? | If yes, how exactly are we dealing with those MBeans? For example, suppose that I use the migration tool to migrate my MBean X to a MC bean. But suppose that another MBean Y, deployed at the MBeanServer, has an attribute that is initialized with the name of old MBean X, and it uses this property internally to look up for X in the MBeanServer. Now that I'm not deploying X as an MBean anymore, Y is hence broken. How do we deal with that? I would do it like this. Ask if all beans should get @JMX: (a) yes, all (b) none (c) prompt for every mbean If (b) is used then the new bean name is previous mbean name. For (a) and (c) I would make a plugable mechanism. e.g. -Dname_transformer=org.jboss.mc.tools.naming.UseServiceProperty Where this naming class would know how to create a new bean name from the old mbean name. Or it could force a prompt, while already suggesting some name. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230946#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...