[
https://issues.jboss.org/browse/WFCORE-4185?page=com.atlassian.jira.plugi...
]
Brian Stansberry resolved WFCORE-4185.
--------------------------------------
Resolution: Rejected
This is invalid. When ReadMasterDomainModelUtil is doing this work, it is processing a
*transformed* resource tree. It cannot reason correctly about the contents of such a tree
solely using the data in the ManagementResourceRegistration.
The JGroups subsystem, for example, places a 'type' attribute in the transformed
resource model, for use by legacy HCs that expected it. That attribute is not present in
the current MRR as it is not needed.
Conceivably we could only strip registered attributes that are runtime-only, but even then
it is conceivable that a legacy version of the subsystem needed the value.
ReadMasterDomainModelUtil is including runtime-only attributes in
what it provides
----------------------------------------------------------------------------------
Key: WFCORE-4185
URL:
https://issues.jboss.org/browse/WFCORE-4185
Project: WildFly Core
Issue Type: Bug
Components: Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Minor
Some resources (e.g. WildFly's transaction subsystem's log-store resource) may
use the Resource tree DMR model node to store non-persistent, runtime-only state. If this
is done, any such value should not be propagated to a remote HC.
(This is actually very unlikely to happen in practice as runtime-only attributes are not
typically used in the domain model. It does affect transformer testing though as
transformer tests usually don't take care to inform their extension that they are
running in an HC.)
Cleaning this up helps resolve WFCORE-4183 by removing irrelevant data that confuses
domain mode transformer tests.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)