CONGRATULATIONS SEBASTIEN!
THIS IS THE COOLEST STUFF!
Just in case you don't realize what that means... it means jboss still runs
from ejb-jar.xml and if you provide jboss.xml YOU ONLY NEED TO SPECIFY WHAT
YOU WANT TO SPECIFY AND NOTHING MORE.
in clear no more "containerconf" if you provide just the overwritten
jndi-name.
The configuration is "incremental".
We are now where we wanted to be: you provide a jboss.xml ONLY if you want
to and the default is NO JBOSS.XML at all. If you want advanced stuff you
put JUST THE DIFF.
Sorry if I am very excited, I have been wanting this for ever :)))))
again congratulations Sebastien, this is kick ass work my friend...
kind regards
marc
PS: Yes we will document that very clearly in the trails.
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Sebastien Alborini
> Sent: Friday, August 11, 2000 6:04 PM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: [jBoss-Dev] New metadata package
>
>
> Hi,
>
> I've just commited the new metadata package in CVS. All the metadata
> related to ejb-jar.xml and jboss.xml is now read by this package, and
> there is no more dependencies on ejx classes.
>
> jboss now loads the xml files is the following order:
> - META-INF/ejb-jar.xml (always)
> - defaultjboss.xml (always)
> - META-INF/jboss.xml (if provided)
>
> This means that the defaults are always loaded, and that you no longer
> have to provide a jboss.xml file.
>
> Furthermore, if you do provide the jboss.xml file, you no longer have to
> copy/paste all the container-configuration stuff: only give what differs
> from the default behaviour. A jboss.xml DTD will be provided soon.
>
> What remains to be done is
> - update the docs
> - continue with jaws.xml, so that we no longer need the
> org.jboss.ejb.deployment package, at least for jboss.
>
> I've tested the new stuff with TestBeans.jar and it seems to work, but
> please report any new bugs that will probably appear, we love new bugs
> :)
>
> Regards,
>
> Sebastien
>
>
