> I'm trying really hard to understand what kind of variability you are going
> for here and failing totally. When would you not want to start logging,
> info, shutdown, and the xml-based mbean loading/classloading/starting
> framework first and in that order? Can you give a concrete scenario?
It is not really that I don't want to start them, I might want to change the
configuration (like for logging). Also I might want to setup my enviornment
differently, say giving each node a seperate directory for config and
other state, but have it load jars from a common directory.
/jboss/share/lib/etc
/jboss/node0/conf/...
/jboss/node1/conf/...
> Among the command line parameters, I see a use in the libDir to indicate
> where the log4j and initial mbean classes (jboss-spine.jar) are, and the
> url of the configuration. I don't see much use in patch or installation
> directory. The configuration would either be a .sar including all needed
> classes or an *-service.xml with a classpath referencing all classes.
I have never used patchdir, but if others use it (which I think scott said
he did) then leave it, it does not cause any immidate problems.
> I'm not very clear about exactly what needs to be on a local machine when
> you start jboss. I think the Main class ;-)... and it looks like the
> jmxri.jar to get the mbean server going... what else? Do we want to try to
> minimize this? Download the jmxri (or replacement)?
I think that is about it.
> I'm mostly really curios about what situation you would want to start the
> pre-jboss-service.xml stuff in a different order or with different
> components -- or did I completely miss what you are talking about?
It is more that I would like to move that out of Main, into the main
jboss-server.xml.
But even more so, I want to init logging first, then go to town from there.
I would also like to see the libdir and other configuration values settable
as properties or by xml elements.
I started playing with an example of what that config might look like, but
it still needs some work.
Basically I think that we can remove some of the specifics from Main, turn
it into a simple xml parser, which reads a <boot> element (or something) for
the initial config order and configuration params. If that is not there,
then it can read a boot.xml from resource (which would be packaged up in
run.jar.
It will use the bits from <boot> to do basically what Main does. This will
allow jboss to be adapted to configurations which we have not even begun to
think of yet.
--jason
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
