[jboss-dev-forums] [Design of JBoss Tools (dev)] - Re: JBoss AS - Starting, Stopping, Polling in AS 5

[scott.stark@jboss.org]

run.jar is used as an executable jar without any additional startup classpath? I can't see how that would work. The run scripts setup additional classpath and endorsed library entries that are needed as well. I expect the tools server setup supports this as well. The question is, what builds the full java command to launch the server?

Eventually I would like to have a self describing osgi like bundle for startup/shutdown.

We should be moving to a proper javax.management.remote.JMXConnector implementation that allows access to the jdk jmx even for minimal jboss configurations without the jmx/invoker/RMIAdaptor as the way to access jmx. While we don't need a jmx kernel in jbossas5 (it is still deployed by default), we should still be mirroring key mcbeans that make up the tooling interface available via jmx for a consistent api. The jboss.system:type=Server mbean is still available in jbossas5.

I'll create jira issues for all these to track them.




View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4120653#4120653

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4120653