[
https://issues.jboss.org/browse/WFLY-10300?page=com.atlassian.jira.plugin...
]
Brian Stansberry updated WFLY-10300:
------------------------------------
Description:
Any /deployment=*/subsystem=xyx resource should be declared as runtime only.
The integration suite should include a check of this, at least for the standalone server
profile we cover in the main part of the testsuite. If it can easily be covered for all
profiles even better. (We test all profiles in admin-only, but subsystems may not register
their /deployment=*/subsystem=x definition in an admin-only server.)
Part of this task should be verifying that the setFeature(false) changes for WFLY-10299
are no longer needed once this is corrected, and if so removing them. (If they are still
needed then why needs investigation.)
Note that WFCORE-3432 eliminates the need to add setRuntimeOnly to children of
/deployment=*/subsystem=xyx as it automatically ensures that a runtime-only parent only
has runtime-only children.
was:
Any /deployment=*/subsystem=xyx resource should be declared as runtime only.
The integration suite should include a check of this, at least for the standalone server
profiles where we create non-admin-only servers.
Part of this task should be verifying that the setFeature(false) changes for WFLY-10299
are no longer needed once this is corrected, and if so removing them. (If they are still
needed then why needs investigation.)
Note that WFCORE-3432 eliminates the need to add setRuntimeOnly to children of
/deployment=*/subsystem=xyx as it automatically ensures that a runtime-only parent only
has runtime-only children.
Mark deployment subsystem resources as runtime-only
---------------------------------------------------
Key: WFLY-10300
URL:
https://issues.jboss.org/browse/WFLY-10300
Project: WildFly
Issue Type: Task
Components: Management
Reporter: Brian Stansberry
Fix For: 13.0.0.Beta1
Any /deployment=*/subsystem=xyx resource should be declared as runtime only.
The integration suite should include a check of this, at least for the standalone server
profile we cover in the main part of the testsuite. If it can easily be covered for all
profiles even better. (We test all profiles in admin-only, but subsystems may not register
their /deployment=*/subsystem=x definition in an admin-only server.)
Part of this task should be verifying that the setFeature(false) changes for WFLY-10299
are no longer needed once this is corrected, and if so removing them. (If they are still
needed then why needs investigation.)
Note that WFCORE-3432 eliminates the need to add setRuntimeOnly to children of
/deployment=*/subsystem=xyx as it automatically ensures that a runtime-only parent only
has runtime-only children.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)