FYI, I think I understand the root of the "init" discussion, it has to do with conflicting views of the same code.
The system view, for example the deployer, well the deployer instanciates, configures, initializes and starts the service. So from the JBoss view the steps are "create and configure" the mbean (through the xml stuff) and then "call init start" in the mbean but when you live in the mbean you only see "init and start" and these are clearer as create/destroy for the service and start/stop for the service. So the bottom line is that init makes sense when you look at it from the system standpoint of JBoss, from the internals, but makes less sense for the one implementing the service, really the user of JBoss. I am all for clear semantics FOR THE USER of JBoss (in this case the developer of an advanced service on Rabbit Hole microkernel stuff) hence my mail of the other day. This is just a FYI that I think I understand the rickard rational behind the "init" call from the MBean view. ______________________________________________________________________ View: http://jboss.org/forums/thread.jsp?forum=66&thread=5344 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
