[jboss-jira] [JBoss JIRA] (WFCORE-342) Streamline :read-resource-description

[Brian Stansberry (JIRA)]

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

Brian Stansberry moved WFLY-1092 to WFCORE-342:
-----------------------------------------------

        Project: WildFly Core  (was: WildFly)
            Key: WFCORE-342  (was: WFLY-1092)
    Component/s: Domain Management
                     (was: Domain Management)


> Streamline :read-resource-description
> -------------------------------------
>
>                 Key: WFCORE-342
>                 URL: https://issues.jboss.org/browse/WFCORE-342
>             Project: WildFly Core
>          Issue Type: Feature Request
>          Components: Domain Management
>            Reporter: Heiko Braun
>
> We have a need for a streamlined read-resource-description operation response. In many cases we only need the attribute descriptions and from those descriptions only a subset of the meta data available. 
> For instance: 
> {noformat}
> "enable-statistics" => {
>                 "type" => BOOLEAN,
>                 "description" => "Whether statistics should be enabled.",
>                 "expressions-allowed" => true,
>                 "nillable" => true,
>                 "default" => false,
>                 "access-type" => "read-write",
>                 "storage" => "configuration",
>                 "restart-required" => "all-services"
>             }
> {noformat}
> Clients that require information about the structure don't need:
> - access-type
> - storage
> - restart-required
> In many cases we don't even need 
> - operations
> - children
> Would it be possible to further parametrize the read-resource-description operation to allow these distinctions? This would help to reduce the overall payload size when clients communicate with the DC and improve thus improve the overall performance. Not to mention parsing greatly benefits from a streamlined model as well.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)