<div dir="ltr">I see your point grouping similar attributes as one ObjectType attribute. For HAL it's always easier to work with simple attributes. This is especially true for automatically generated UIs.<div><br></div><div>OTOH attributes tuples like {path, relative-to} are quite common. The logging subsystem uses them in various resources. So adding support for those tuples seems reasonable (in fact we already support them in HAL.next). So keeping them for /subsystem=elytron/properties-realm=* is ok for me.<div><br></div><div>What we should avoid though are deeply nested attributes. (e.g. lists inside objects)</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 28, 2016 at 1:16 PM, Darran Lofthouse <span dir="ltr"><<a href="mailto:darran.lofthouse@jboss.com" target="_blank">darran.lofthouse@jboss.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">A number of resources have been flagged within the Elytron subsystem<br>
requesting that we review the use of ObjectTypes (and similar) within<br>
the resource definitions.<br>
<br>
Some I know we can simplify but others I would like to get a second<br>
opinion on, firstly I wanted to look at the 'properties-realm' resource.<br>
<br>
<a href="https://gist.github.com/darranl/ef7b06222e4dbe7ba242f7a5a2da991e" rel="noreferrer" target="_blank">https://gist.github.com/<wbr>darranl/<wbr>ef7b06222e4dbe7ba242f7a5a2da99<wbr>1e</a><br>
<br>
This is a realm implemented to make use of the legacy properties files<br>
users of AS7 through WF10 will be familiar with so we need to reference<br>
two different properties files with the group-properties being optional.<br>
<br>
Where a file is referenced it is common to reference both a path and a<br>
relative-to, rather than looking to find unique names for two path<br>
attributes and unique names for two relative-to attributes I have<br>
wrapped in specific OBJECT type attributes.<br>
<br>
I could achieve a similar grouping by flattening and using attribute<br>
groups but then the path and relative-to attributes would require unique<br>
names. Personally I just felt that for two attributes always used as a<br>
pair it was cleaner to wrap them into one.<br>
<br>
Note: Checking the output myself the path should not be nillable and<br>
the relative-to should not allow expressions so those two will be corrected.<br>
<br>
Regards,<br>
Darran Lofthouse.<br>
______________________________<wbr>_________________<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" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/wildfly-dev</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">
---<br>Harald Pehl<br>JBoss by Red Hat<br><a href="http://hpehl.info" target="_blank">http://hpehl.info</a></div></div>
</div>