Hi David
Based on the Marc's presentation about the future of JBoss I see that you
basically JBoss loads and instantiate the
ServiceControl/ConfigurationService
and then "deploys" the MBeans at runtime where there is not difference if
at the startup or in any other part of the life of the application server.
There are some points I want to bring in here:
- when you talking about the classes in the classpath you are talking about
how the classes gets looked up and loaded which is different from the
instantiation of the objects (which is like the deployment of the EJBs and
creations of the EJBs through create() or the finder methods).
- we could use application specific classloaders which would allow to
undeploy
the class the MBeans are based on (or to load the new classes in the new
classloader).
- The service.xml (or service deployement descriptor) declares what
instances
of MBeans are created (name, constructor arguments and attributes). We
should maybe also add (what someone else brought up earlier) an operation
tag allowing the deployement descriptor what operations to call (right
know
we assume that this would be init() and start()) but this wouldn't be true
for
applications specific MBeans).
Mad Andy
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
