[
https://issues.jboss.org/browse/WFLY-10784?page=com.atlassian.jira.plugin...
]
Brian Stansberry commented on WFLY-10784:
-----------------------------------------
[~manovotn] Another approach you can use is DeploymentUnit.putAttachment. That allows DUPs
to pass data to each other via the DeploymentUnit. So WeldSubsystemAdd could attach the
WeldBootstrapService. Passing services that way feels vaguely yucky, but no more so than
doing
DeploymentPhaseContext.getServiceRegistry().getService(WeldBootstrapService.SERVICE_NAME).
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)