[
https://issues.jboss.org/browse/WFCORE-2497?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFCORE-2497:
------------------------------------------
[~dlofthouse] The way the WFCORE-1106 stuff works, if the child provides it's own
capability, a parent resource being reload-required would only prevent Stage.RUNTIME
execution by the child resource if the child's capability depends on the parent's.
So no, there is no implicit dependency.
For Core 4 we could consider auto-adding such a dependency as a programming convenience,
perhaps following rules similar to what WFCORE-1106 did for finding letting children
without capabilities find ones registered by the parent. I'll think a bit about how
hard that would be to do sooner, but I'm concerned about cramming stuff in late in the
cycle.
Convert *-authentication-factory resources to be child resources of
security-domain
-----------------------------------------------------------------------------------
Key: WFCORE-2497
URL:
https://issues.jboss.org/browse/WFCORE-2497
Project: WildFly Core
Issue Type: Task
Components: Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 3.0.0.Beta10
This is a good example of where child resources work.
The authentication factory resources have a mandatory dependency on a single security
domain.
The configuration within the factory is related to it's security domain.
There is only a single resource that can provide security domains.
The behaviour of the parent is unaffected by the existence or configuration of the
child.
The parent and child manage their own services independently with the child's service
depending on the parent's service.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)