[jboss-as7-dev] Recent profile changes

David M. Lloyd david.lloyd at redhat.com
Mon Jul 4 11:11:09 EDT 2011


Inline.

On 07/04/2011 02:50 AM, Heiko Braun wrote:
>
> Makes sense from your point of view, but for tools or users it's difficult to maintain
> the proper source address and dealing with circular references.
>
> Let's say profile B includes profile A. Profile A declares subsystem Foo.
>
> Can we support both?
>
> /profile=B/subsystem=Foo:write-attribute
>
> and
>
> /profile=A/subsystem=Foo:write-attribute

I would say "no".  This not only makes sense from our point of view but 
yours as well.  If they change an attribute in an inheriting profile, it 
will change it for the other profile as well, and for all profiles which 
include that profile, which can cause some major surprise.

> The point is that for most management tasks, it doesn't matter that the effective profile
> actually consists of an inclusion hierarchy. I believe people care about the subsystem "Web" configuration
> for a particular server, regardless of it's origin. So forcing them to deal with the inclusion hierarchy
> doesn't make sense to me. I don't see the added value.
>
> Apart from that there are other, related questions that we need address:
>
> - Are subsystem re-declarations allowed within an inclusion hierarchy?

IIRC No.

> - What's the policy for this: replace or merge?
>
> I think once these questions are answered we'll easily find a solution to the questions above.
>
> Ike
>
>
> On Jul 2, 2011, at 11:56 AM, Kabir Khan wrote:
>
>> I prefer it the way we have it set up now, but with the ability to see but not modify inherited stuff easily.
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev


-- 
- DML


More information about the jboss-as7-dev mailing list