[jboss-jira] [JBoss JIRA] (AS7-2333) :read-resource should also show r/w status and whether restart is required

[Brian Stansberry (Updated) (JIRA)]

     [ https://issues.jboss.org/browse/AS7-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated AS7-2333:
----------------------------------

         Assignee: Brian Stansberry  (was: Alexey Loubyansky)
    Fix Version/s:     (was: 7.1.0.Beta1)
      Component/s: Domain Management
                       (was: CLI)


This isn't really a CLI issue; it's a core management API issue.

I disagree that read-resource should provide this; you're requesting a mix of metadata about state and the state itself. The metadata can be obtained via the read-resource-description operation.

I can see the desire for seeing both types of data in some combined format, but it needs to be a separate operation.

>From a practical point of view, changing the existing operation would break every client that exists (console, JON, deployment-scanner, probably CLI features, custom stuff done by others that I don't know about).
                
> :read-resource should also show r/w status and whether restart is required
> --------------------------------------------------------------------------
>
>                 Key: AS7-2333
>                 URL: https://issues.jboss.org/browse/AS7-2333
>             Project: Application Server 7
>          Issue Type: Feature Request
>          Components: Domain Management
>    Affects Versions: 7.1.0.Alpha1
>         Environment: all
>            Reporter: Rich Sharples
>            Assignee: Brian Stansberry
>              Labels: eap6-ux
>
> :read-resource could provide some more useful information :
> some attributes can't be changed (eg. they are ports generated from an offset) - :read-resource output should show the attributes that are read-only.
> some attributes require a restart to take effect - :read-resource should make this clear.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira