I've noticed the same issue and agree with your proposal.
-----Original Message-----
From: Toby Allsopp <[EMAIL PROTECTED]>
To: jBoss Users <[EMAIL PROTECTED]>
Date: Tuesday, November 21, 2000 4:28 PM
Subject: [jBoss-User] jboss.xml overriding standardjboss.xml
>Hello.
>
>The comments in ConfigurationMetaData.java suggest that I should be
able
>to define, in my jboss.xml, only those elements in standardjboss.xml
>that I want to change. However, the implementation doesn't seem to
allow
>this.
>
>The comment is:
>// everything is optional to allow jboss.xml to modify part of a
>configuration
>// defined in standardjboss.xml
>
>but the code says:
>containerInvoker =
>getElementContent(getOptionalChild(element,"container-invoker"));
>
>This means that containerInvoker and everything else get set to null if
>I include a jboss.xml that doesn't specify them. I've patched this
>locally to work how I would expect, but surely this has caused problems
>before. Am I missing something or is everyone happy duplicating
>standardjboss.xml in their jboss.xml?
>
>Regards,
>Toby.
>
>P.S. I see that this was brought up by Rick Horowitz but never
>addresses. The latest commit to ConfigurationMetaData.java (by
>"salborini") claimed to fix this but it doesn't seem to.
>
>--
>Toby Allsopp
>Research
>Peace Software International Ltd
>Ph +64-9-3730400
>
>
>--
>--------------------------------------------------------------
>To subscribe: [EMAIL PROTECTED]
>To unsubscribe: [EMAIL PROTECTED]
>Problems?: [EMAIL PROTECTED]
>
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
