[jboss-jira] [JBoss JIRA] (WFCORE-459) Account for attribute groups in CLI behavior

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13361520#comment-13361520 ] 

Brian Stansberry commented on WFCORE-459:
-----------------------------------------

[~jdenise] Very few are. In most cases there's no need for any grouping beyond the resource itself.

Anything on this should be deferred to WF Core 4, as it's late for 3.

Re: the sorting of attributes in the server's read-resource response, I believe they may be sorted by group if there is one, but QE has filed a JBEAP to get rid of that and always sort by name . We'll likely follow through on that. In a higher level view like 'ls', grouping provides benefit, assuming the group is displayed. But for low-level read-resource the group name is not part of the output, and in that case sorting the attributes by group ends up producing what looks like a random sort.

> Account for attribute groups in CLI behavior
> --------------------------------------------
>
>                 Key: WFCORE-459
>                 URL: https://issues.jboss.org/browse/WFCORE-459
>             Project: WildFly Core
>          Issue Type: Feature Request
>          Components: CLI
>            Reporter: Brian Stansberry
>            Assignee: Jean-Francois Denise
>             Fix For: 3.0.0.Beta1
>
>
> See http://lists.jboss.org/pipermail/wildfly-dev/2014-December/003414.html
> This JIRA is for reflecting the attribute group notion in CLI behavior.
> I think this is just reflecting it in the output of the "ls -l" command, although there may be other places I'm not thinking of. For "ls -l" simplest is just to add a GROUP column to the right, and then sort the attributes by group and then by name, but perhaps something else is better.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)