Ok, Jason,
there was already a superior way which was the "MBean MLet" boot file. And I
have removed it for several reasons.
1- I wanted to be done
2- having the .boot file around doesn't add much but complicates life and
administration (FAQ: Do I change boot.xml?)
3- we *never* change it except when there is a new JAXP version out that we
want to use.
configurability is good when it is needed, in this case it is not (imho,
feel free to flame). Therefore "simple is the word...."
marcf
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Jason
|Dillon
|Sent: Friday, September 07, 2001 6:43 PM
|To: [EMAIL PROTECTED]
|Subject: [JBoss-dev] use resource properties file to drive boot sequence
|
|
|In Main currently we hardcode serveral MBean creations. Why not read a
|autoload.properties (or whatever) from run.jar, which lists the sequence,
|then simply iterate over it and startup components:
|
| component.0=org.jboss.logging.Logger
| component.1=org.jboss.logging.Log4jService
| component.2=org.jboss.system.Info
| component.3=org.jboss.system.Shutdown
| component.4=org.jboss.system.ServiceController
| component.5=org.jboss.deployment.ServiceDeployer
|
|This could be XML too, but properties will work just as well.
|
|--jason
|
|
|_______________________________________________
|Jboss-development mailing list
|[EMAIL PROTECTED]
|https://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
