[
https://issues.jboss.org/browse/WFCORE-3432?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFCORE-3432:
------------------------------------------
It looks like 3) is problematic, as currently
/deployment=foo.war:read-resource(recursive=true, include-runtime=false) is returning the
subsystem children, even though it shouldn't. :( So fixing the MRR may break users
who are counting on the bug, including Arquillian -- see WFARQ-35.
Correct ManagementResourceRegistration runtime-only metadata
------------------------------------------------------------
Key: WFCORE-3432
URL:
https://issues.jboss.org/browse/WFCORE-3432
Project: WildFly Core
Issue Type: Task
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
We have MRRs, e.g. ServerEnvironmentResourceDescription, where the resources are
runtime-only but the MRR.isRuntimeOnly() is not stating that.
3 possible aspects to this:
1) Audit uses of Resource.Factory.create(true[,...]) and check that those are also
setting up the ResourceDefinition correctly so the MRR reports runtime-only.
2) Change the ConcreteResourceRegistration stuff such that it ignores the
ResourceDefinition if the parent is runtime-only. IOW, runtime-only parents can't have
non-runtime-only children. This would wipe out a category of possilbe errors in the setup
of the children.
3) Have ExtensionRegistry/SubsystemRegistrationImpl ensure that the registrations for
deployment resource children are runtime-only.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)