On 7/5/11 11:00 AM, Brian Stansberry wrote:
On 7/4/11 5:01 AM, Heiko Braun wrote:
>
>
> Well, you could still:
>
> - re-use configurations
> - configure certain options once, in a single place
> - simplify and cleanup the xml files
>
> There is two ways to look at it:
>
> a)<includes/> can reduce redundancy with certain constraints
> b) or it may be the ultimate super weapon that allows duplicate declarations and
overwrites
>
>
> But if you chose b) please answer this question first:
>
>
> Profile C includes profile B. A includes B and C. All of them declare subsystem
"Web".
> Now you change the socket binding for subsystem "Web" in Profile B.
>
> What socket binding do servers use that rely on profile A?
>
*If* we supported overrides, it would be on a complete replace basis for
the subsystem. So, you said A declares subsystem "Web" so it's own
configuration would determine things.
I Agree. One thing we have learned about overrides, is that they aren't
worth doing if they don't have simple, easy to understand rules.
--
Jason T. Greene
JBoss, a division of Red Hat