[
https://issues.jboss.org/browse/WFLY-10784?page=com.atlassian.jira.plugin...
]
Jason Greene commented on WFLY-10784:
-------------------------------------
[~manovotn] There is a cleanup phase in our deployers that is used for similar things like
this. So you could insert a deployer there to release state. As to a general replacement
for optional services, utilizing the capabilities and requirements facility of WildFly is
often a good choice. You can also have passive services where the service only comes up if
its dependency is also up. However I think both of these are unlikely to be a good fit,
based on your description of the problem.
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)