RE: [JBoss-dev] Moving out the core hard-coded serviceconfiguration

[Scott M S. <sco...@jb...>]

I don't see a chicken/egg problem for the JBoss services which is what I =
want
to address now. Trying to do the same for the embedded JMX services is
a second step.
=20
I was just thinking of using a system property to specify the xmbean =
resource
location in the same manner in which the conf/jboss-service.xml =
descriptor
is used, and would default to a conf/xmbeans directory (the current =
conf/xmdesc
would be renamed).
=20
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx

________________________________

From: jbo...@li... on behalf of Adrian =
Brock
Sent: Wed 1/7/2004 10:28 AM
To: jbo...@li...
Subject: Re: [JBoss-dev] Moving out the core hard-coded =
serviceconfiguration



On Wed, 2004-01-07 at 18:04, Scott M Stark wrote:
> A long standing issue I have with the jmx microkernel of services
> that are hard-coded (ServerImpl, MainDeployer, SARDeployer,
> ServiceController, ...)
> is that there is no way to configure these services let alone replace
> them.
>
> So, I want to externalize these as XMBeans. Comments?
>

Couldn't we just use an xml (xmbean) description of these services in
jboss-system.jar
Then use Classloader.getResource() to load it.

If somebody wants to override the xml they can use the patch
parameter (or add it JBOSS_CLASSPATH)
to insert an alternate xml file before jboss-system.jar
in the kernel's classloader.

The same could be done for the hard-wired modelmbean descriptions
in MBeanServerImpl.

Depending upon how far you want to go, we could also provide
a file that contains a list of mbeans descriptors to instantiate
that forms the kernel.

In principal this could all be handled by the mbean server.
i.e. When creating the MBeanServer it looks in a certain location
for the initial mbeans to load.
Bootstrapping the server would just be to setup the classloader
then create an MBeanServer.

I imagine there are a number of "chicken/egg" problems to solve.

Regards,
Adrian

--
xxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Director of Support
Back Office
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx