Hi
Instead of loading CS by default from Main.java why not loading jboss.jcml
by default and using a <server> tag to figure out which CS to load. Example:
<server cs="org.jboss.whatsoever" lib="jboss.jar">
I would advocate to kick "jboss.conf" out otherwise I think we wouldn't gain
anything from this effort, do we?
Andy
> -----Original Message-----
> From: marc fleury [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 10, 2001 12:22 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-dev] Main.java, let's clean it up
>
>
> The CS works from XML, the jcml files needs that already,
> chicken and egg.
>
> what I was thinking about is
> 1- we keep the jboss.conf with just the CS/XMLet start
> 2- or we force loading the CS from the main (always) as the
> front end for
> the XMLet mechanism.
>
> BTW, XMLet is our own JBoss extension of the default MLet mechanism,
>
> marc
>
> |-----Original Message-----
> |From: [EMAIL PROTECTED]
> |[mailto:[EMAIL PROTECTED]]On Behalf Of
> |Schaefer, Andreas
> |Sent: Thursday, May 10, 2001 12:51 PM
> |To: '[EMAIL PROTECTED]'
> |Subject: RE: [JBoss-dev] Main.java, let's clean it up
> |
> |
> |How's about specifying the Configuration Service in the <server>
> |tag within the JCML file.
> |
> |Then the Main.java can start to read the JCML file and then
> hand it over
> |to the found Configuration Service.
> |
> |MAD Andy
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
