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.
Ike
On Jul 4, 2011, at 11:29 AM, Heiko W.Rupp wrote:
> Then I don't really see the use case of different inheriting profiles.
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat