[jbossts-issues] [JBoss JIRA] (JBTM-3293) LRA coordinator jar cannot be deployed on WildFly
[
https://issues.redhat.com/browse/JBTM-3293?page=com.atlassian.jira.plugin...
]
Ondrej Chaloupka commented on JBTM-3293:
----------------------------------------
[~mstefank] ok, I see. Would then make sense to consider of not publishing the {{jar}}
archive type to Maven nexus but only the {{war}} archive. And using the jar only as a
deliverable for the internal projects?
Or are not the thorntail and quarkus capable to work with {{war}} in the same way as with
{{jar}}?
(I assume here that the jar is now consumed only for the Narayana purposes. When consumed
e.g. by OpenLiberty it's wrong as the {{war}} should be provided for them.)
LRA coordinator jar cannot be deployed on WildFly
-------------------------------------------------
Key: JBTM-3293
URL: https://issues.redhat.com/browse/JBTM-3293
Project: JBoss Transaction Manager
Issue Type: Bug
Components: LRA
Affects Versions: 5.10.4.Final
Reporter: Martin Stefanko
Assignee: Martin Stefanko
Priority: Major
Fix For: 5.next
I am not sure whether this should be possible but the lra-coordinator.jar from
lra-coordinator-jar module can't be deployed on latest WildFly. The deployment fails
with the following error:
{noformat}
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied
dependencies for type LRAService with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject
io.narayana.lra.coordinator.api.RecoveryCoordinator.lraService
at
io.narayana.lra.coordinator.api.RecoveryCoordinator.lraService(RecoveryCoordinator.java:0)
WELD-001474: Class io.narayana.lra.coordinator.domain.service.LRAService is on the
classpath, but was ignored because a class it references was not found:
com.arjuna.ats.arjuna.recovery.RecoveryModule from [Module
"deployment.lra-coordinator.jar" from Service Module Loader].
{noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)