]
Jason Greene updated WFLY-202:
------------------------------
Fix Version/s: 8.0.0.Final
Include registered attributes with no model representation in
read-resource results
-----------------------------------------------------------------------------------
Key: WFLY-202
URL:
https://issues.jboss.org/browse/WFLY-202
Project: WildFly
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Domain Management
Reporter: Brian Stansberry
Priority: Minor
Fix For: 8.0.0.CR1, 8.0.0.Final
Following situation:
1) resource includes attribute xyz
2) No read-handler is registered for xyz (i.e. default read semantic
Resource.getModel().get("xyz") is to be used)
3) Poorly coded "add" handler for the resource doesn't call
model.get("xyz") for some reason.
The effect of this is the read-resource result will not include "xyz" =>
undefined in the output. Nothing for xyz will appear at all, hiding the existence of the
attribute from the caller.
The read-resource handler can deal with a check in its loop through the AttributeAccess
registration for the "no read-handler" case. (This check is already there; an
'else' clause is needed.) If no read-handler, see if there is an entry in the
directAttributes map for the attribute; if not, add one with a value of new ModelNode().
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: