[jboss-jira] [JBoss JIRA] (WFLY-3306) Inconsistent responses between read-children-types and read-children-names or read-children-resources

[Brian Stansberry (JIRA)]

Brian Stansberry created WFLY-3306:
--------------------------------------

             Summary: Inconsistent responses between read-children-types and read-children-names or read-children-resources
                 Key: WFLY-3306
                 URL: https://issues.jboss.org/browse/WFLY-3306
             Project: WildFly
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Domain Management
    Affects Versions: 8.1.0.CR1, 8.0.0.CR1
            Reporter: Brian Stansberry
            Assignee: Brian Stansberry
            Priority: Minor
             Fix For: 9.0.0.CR1


The read-children-types op is implemented by reading the names of the NodeSubregistry objects in the target resource's ManagementResourceRegistration. The read-children-names and read-children-resources ops are implemented by reading the full PathElement of registered child MRRs.

It's possible these two can get out of sync, as a NodeSubregistry can be added in order to support a submodel, but such subregistries aren't removed if all children are removed. This manifests itself in EAP 6 with the 'server' child type. See https://bugzilla.redhat.com/show_bug.cgi?id=1093030. (Note WF should not have this specific problem, as WF registers a generic MRR for 'server'.)

Fix is for GlobalOperationHandlers.getChildAddresses() to include an entry with an empty value for any valid child type. This will ensure the responses are consistent.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)