[
https://issues.jboss.org/browse/WFLY-10784?page=com.atlassian.jira.plugin...
]
Brian Stansberry commented on WFLY-10784:
-----------------------------------------
[~mkouba] You're right. Sorry, and thanks for realizing this.
Another possibility is to use a org.jboss.msc.service.StabilityMonitor in a Phase.CLEANUP
DUP or perhaps better in WeldStartCompletionService.start. Instead of depending on
services you register their ServiceController with the StabilityMonitor and then
awaitStability.
Doing it in a service means that other DUPs in that same Phase won't have to wait to
execute until stability is reached. It shouldn't be done in a Phase.INSTALL DUP.
WeldStartCompletionService failed when optional components not
installed
------------------------------------------------------------------------
Key: WFLY-10784
URL:
https://issues.jboss.org/browse/WFLY-10784
Project: WildFly
Issue Type: Bug
Components: CDI / Weld
Affects Versions: 12.0.0.Final, 13.0.0.Final
Reporter: Alexander Kudrevatykh
Assignee: Matej Novotny
Attachments: arq-test.tar.xz
WebComponents are optional and fail in initialising it not causes fail of deployment, but
when starting EAR application with included WAR fail in deployment since Wildfly 12
because WeldStartCompletionService depends on all components regardless of their type
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)