[JBoss-dev] JBAS-1841 - There is no spoon

[Adrian Brock]

In another attempt to weed MCF code from codebase :-)
the JMX ServiceController has now been replaced by a
Microcontainer facade.

A more complete description of the status can be found here:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=88071

Please report problems as either subtasks on the JIRA issue:
http://jira.jboss.com/jira/browse/JBAS-1841
or create a thread in the POJO forum
http://www.jboss.com/index.html?module=bb&op=viewforum&f=208

FAQ:

Q: Does this mean JMX is no longer supported?
A: No, JMX is another context type in the generic dependency
controller. There are now two types, JMX and POJO
that will be able to cross inject dependencies amongst 
themselves.

Q: Do I need to convert my MBeans to POJOs?
A: No the whole of this is to support in the new POJO
environment both JBoss developers and users who have written MBeans 
as integration into JBossAS. This provides backwards
compatibility.

Q: My MBean no longer works properly?
A: Assuming you didn't break it :-), use one of the
links above.

Q: Is this documentated anywhere?
A: You're kidding right? I will write up a description
of how it works shortly. Those famailiar with the POJO
microcontainer will understand the basics if you 
do the following "pseudo" replacements:

POJO -> JMX
Instantiate: new() -> createMBean();
Configure: setX() -> setAttribute("X");
etc.

Q: Why are the ServiceCreator/Configurator deprecated?
A: These were never intended to be used externally.
They are implementation details of the ServiceController
(as the javadoc describes "A helper class for the ServiceController")

In fact, if you use the ServiceConfigurator directly,
you are almost certainly leaking memory nor will it work
properly unless you are very lucky. :-)
-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxx