<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 10, 2014 at 4:52 PM, Brian Stansberry <span dir="ltr"><<a href="mailto:brian.stansberry@redhat.com" target="_blank">brian.stansberry@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class=""><div class="h5">On 12/10/14, 9:22 AM, Kabir Khan wrote:<br>
><br>
>> On 9 Dec 2014, at 21:00, Brian Stansberry <<a href="mailto:brian.stansberry@redhat.com">brian.stansberry@redhat.com</a>> wrote:<br>
>><br>
>> Off and on we've had discussions around the idea of "attribute groups".<br>
>> We've got some use cases that are crying out for such a thing[1], so I'd<br>
>> like to propose doing something concrete but simple for these for WF 9,<br>
>> ideally in the next month.<br>
>><br>
>> A big part of my goal here is to ensure that whatever we do doesn't<br>
>> preclude something more advanced in any next generation management<br>
>> stuff, e.g. David's stuff.<br>
>><br>
>> PART I Concepts<br>
>><br>
>> 1) What is an attribute group?<br>
>><br>
>> The "attribute group" concept I propose is simply a collection of<br>
>> attributes associated with the same resource type that are independently<br>
>> configurable but are statically declared to be conceptually related. The<br>
>> group has a name, and members. The name provides a brief indication of<br>
>> the nature of the relationship.<br>
>><br>
>> The goal is to provide information to the user to help them better<br>
>> understand the relationship between attributes. In particular,<br>
>> management tools could use this information to visually present related<br>
>> attributes together, e.g. in a tab or other grouping widget in the web<br>
>> console.<br>
>><br>
>> 2) What isn't an attribute group?<br>
>><br>
>> Something relevant to writes.<br>
>><br>
>> 3) Why would I use a child resource instead of an attribute group?<br>
>><br>
>> Because the attributes control a discrete piece of functionality and you<br>
>> need to be able to turn that on or off as a unit. So you add/remove the<br>
>> resource.<br>
>><br>
>> 4) Why would I use a complex attribute with a bunch of fields instead of<br>
>> n>1 simple attributes in a group.<br>
>><br>
>> a) Because the attributes control a discrete piece of functionality and<br>
>> you need to be able to turn that off as a unit. So users can undefine<br>
>> the complex attribute.<br>
>><br>
>> b) Because it's a common use case that modifications to n>1 of the<br>
>> fields should be done atomically and you don't want to force users to<br>
>> use a CLI batch. So you let them use write-attribute and specify the<br>
>> value of all the fields.<br>
> Why not something along the lines of :write-attribute-group(name=mygroup, value={attr1=a, attr2=b})?<br>
> Internally that could create a composite for us, giving complex attribute functionality while avoiding the messy resource descriptions<br>
><br>
<br>
</div></div>On the branch of the thread where I'm discussing with Tomaz, he raised<br>
the same idea, which I think is a good one. I think a "write-attributes"<br>
with no relationship to attribute-group makes more sense though.<br></blockquote><div><br></div><div>In your preamble you said:<br><br>[...] The "attribute group" concept I propose is simply a collection of<br>
attributes associated with the same resource type that are independently<br>
configurable but are statically declared to be conceptually related. The<br>
group has a name, and members. The name provides a brief indication of<br>
the nature of the relationship. [...]<br><br></div><div>Doesn't it clash with your last thought?<br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<span class="im"><br>
--<br>
Brian Stansberry<br>
Senior Principal Software Engineer<br>
JBoss by Red Hat<br>
</span><div class=""><div class="h5">_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
</div></div></blockquote></div><br></div></div>