[
https://issues.jboss.org/browse/WFCORE-1538?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFCORE-1538:
------------------------------------------
I'm fine with not providing this data. It's not at all trivial to provide it
reliably as the kernel can't just get the Resource and call getModel() on it. There is
no requirement that such a call produce the value for all attributes. The handling for
read-resource illustrates what all has to be done to correctly provide all the values.
Basically you have to add read-attribute steps for each attribute.
resource-added notifications contain no data
--------------------------------------------
Key: WFCORE-1538
URL:
https://issues.jboss.org/browse/WFCORE-1538
Project: WildFly Core
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 2.1.0.Final
Reporter: Kabir Khan
Assignee: Brian Stansberry
When listening for notifications, I found that the attribute-value-written notifications
contain a data field containing the name of the modified attribute and the old and new
values.
For resource-added (and presumably resource-removed) the data field is empty, so if
someone has registered a notification handler for resource adds, and they want the values
of the resource attributes they will have to do a read-resource on the newly created
resource.
Should the data for a resource add contain the attribute values?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)