JBossDeveloper

The file is admittedly a bit ugly, but it's really by necessity. It was done this was so it could be transparently wired directly into the service deployer process. When a MBean service is being deployed, it's config portion is passed through the svc binding mgr and dynamically reconfigured based on the svc binding xml file. The service is looked up in the sb config by MBean object name of the service currently being configured (jetty, jnp, etc).

The big advantage to this approach is that no code changes are necessary to the to-be-reconfigured service or its mbean config file in order to be reconfig'd by the svc binding mgr. Also, no code changes are necessary to the svc binding mgr to support a new service. Just add the new service entry to the bindings file.

This all happens on deployment, so each time yoru service is redeployed, it goes through this 'override' process.

Haven't really thught much about a properties-file based solution. I am not sure we could do it and still achieve the same transparency as with the XML today.

See jboss-development archives if you're looking for the design discussions.

Mike

Anyone knows how to use "shutdown.sh" to shut down different JBoss instances?

"cliu" wrote:
Anyone knows how to use "shutdown.sh" to shut down different JBoss instances?