[
https://issues.jboss.org/browse/WFCORE-2497?page=com.atlassian.jira.plugi...
]
Darran Lofthouse commented on WFCORE-2497:
------------------------------------------
Correct, the parent resource is still unaware of it's child so the parent can be added
as one atomic step which will install and start it's services, the child can then be
added as a second atomic step and register it's services.
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)