|
|The new way is to add MBeans to jboss.jcml only. This will create them,
|and apply the settings specified. Once all MBeans have been created,
|initialized, and started, the current settings will be saved to
|jboss-auto.jcml. At runtime you can invoke "saveConfiguration" on the
|"Configuration" MBean (through the HTML admin tool for example) to store
|the current state of the server. A future version of JBoss will store
|settings automatically when they are changed.
he,
you can go wild with the XML javabeans that fire notification of changes :)
|During this upgrade I found a bug in JAXP (the usual "don't use
|Class.forName to load classes dynamically, but the context classloader"
|bug). Sun has been notified, but in the meantime I have added jaxp.jar
|and parser.jar to the application classloader through run.jar's manifest
|file.
good
|I have not yet updated the folowing services:
|* Jetty
julian can you take care of that update?
|Final disclaimer:
|I have tried very hard to make sure that there are no problems with this
|update, but since it is so big it is expected to be a couple of minor
|problems for a couple of days until they are ironed out. Sorry for any
|inconvenience.
right just wasted a day :) and it doesn't look like we are really done
marc
|
|Hope ya like it. I have tried to listen to all comments about
|ease-of-use with regard to the configuration files, but some people
|might still be unhappy with how it works now. Please take any discussion
|regarding this to jboss-dev.
|
|best regards,
| Rickard
|
|--
|Rickard �berg
|
|Email: [EMAIL PROTECTED]
|
|
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
