In the JBoss5, if we register a mbean to mbean server, this mbean will be binded with a JNDI name automaticlly. By the preview JBoss versions, we also can lookup MBeanServer by a JNDI name. Add we can lookup all of the mbeans(registered to boss mbean server by ourself) by JNDI name. But for JBoss7, I can't lookup these MBeans.

Because by JNDI I can lookup a remote object as a local stub, then I can invoke remote object's method like it's in the local JVM. I don't whether JBoss7 don't register every mbean to JNDI server automaticlly. By for JBoss5, I can do this. And I don't think JBoss7 remove this good feature.

So we only can access the remote mbean by the MBeanconnection, if so, that's really bad. Because in JBoss5, I can get a remote mbean by JNDI lookup, then I can invoke the remote mbean's method like what happens in local JVM. I can't believe JBoss7 removed this feature.

JNDI code(vey simple)

// define remote ip, port and authtication parameters in this hashtable.

Hashtable hashtable;

InitialContext ctx = new InitialContext(hashtable);

User user = (User) ctx.lookup("java:/user");

System.out.println(user.getName());