Rickard �berg wrote:
> [EMAIL PROTECTED] wrote:
> > 1) edit jboss.jcml
> > 2) kill jboss
> > 3) jboss writes state to jboss-auto.jcml
> > 4) start jboss
> > 5) jboss loads jboss-auto.jcml
> > 6) jboss performs an overwrite-merge of jboss.jcml
Ok, I have modified the Configuration service to work like that now (not
commited to CVS though). I'm having a bit of trouble with in which order
to do stuff though.
The easiest is:
* load state for all beans, and create MBeans if necessary
* init all beans
* start all beans
The problem is that some of the beans, especially the first ones, really
need to be inited as soon as possible. For example, as soon as the
Logger and ClassPathExtension's are loaded they need to be inited
because they're used immediately after their creation.
So, instead it should be something like
* load/init state for all beans, and create MBeans if necessary
* start all beans
Not sure what I think about this though. It's a tricky one.
Ah well. That's for tomorrow.
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
