Hey Rickard,
I'd like to check it out. But I have a slight problem:
If I do /bin/sh build.sh an error shows up complaining about a missing
JAXP. So I added a reference to jaxp.jar to build.sh but that now leads
to this error:
Buildfile: build.xml
BUILD FAILED
javax.xml.parsers.FactoryConfigurationError:
com.sun.xml.parser.SAXParserFactoryImpl
at
javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:84)
at
org.apache.tools.ant.ProjectHelper.getParserFactory(ProjectHelper.java:656)
at org.apache.tools.ant.ProjectHelper.parse(ProjectHelper.java:101)
at
org.apache.tools.ant.ProjectHelper.configureProject(ProjectHelper.java:85)
at org.apache.tools.ant.Main.runBuild(Main.java:403)
at org.apache.tools.ant.Main.main(Main.java:149)
What to do ?
Tobias
Rickard �berg wrote:
>
> All,
>
> I have now checked in a major update to CVS. The primary change is a new
> configuration scheme.
>
> The old way to add MBeans was to first add them to jboss.conf to get
> them created, and then add settings for the MBean in jboss.jcml. Also,
> jboss.jcml was overwritten at runtime removing any manually added
> comments or similar structural changes.
>
> 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.
>
> jboss.conf is still there, but it is only used for special services, and
> in the normal case you should not have to touch it. JDBC pools are added
> only to jboss.jcml for example.
>
> Check it out, and you will see what I mean. It is pretty
> straightforward.
>
> I have also updated A LOT of services because of this change. The
> primary change has been to add default constructors, and make sure that
> one can call set methods on the MBeans without any problems.
>
> *NOTE! IMPORTANT!*
> For future MBean writers using ServiceMBeanSupport:
> * Do NOT initialize anything in the constructor of the MBean. Do this in
> initService();
> * Do NOT apply new attribute values in set methods if the service uses a
> delegated model (i.e. it wraps the real service). Simply store the
> values in MBean attributes, and apply them in startService(). This is
> because the delegated service should be initialized in initService() and
> set methods may be called prior to that has been done.
> These two rules will ensure that services behave well.
>
> 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.
>
> I have not yet updated the folowing services:
> * Jetty
> * JDBC connection pool (the XA conncetion pool has been updated)
>
> Some code has been updated to use JAXP instead of an XML parser
> directly. This will make it easier to change XML parser if necessary.
>
> All source files have changed the header to:
> * Say "JBoss" instead of "jBoss", which is the new official name
> * Say "LGPL" instead of "GPL", which is the current license used
>
> The "JMX bug" which corrupted the jboss.jcml has been avoided (I think).
> It seems the JMX RI does not like "isFoo" as get method (i.e. it needs
> to be "getFoo"). I have updated the XA connection pool, which was
> affected by this, and the problem seems to have gone away.
>
> 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.
>
> 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]
