[
https://issues.redhat.com/browse/JBTM-3293?page=com.atlassian.jira.plugin...
]
Ondrej Chaloupka commented on JBTM-3293:
----------------------------------------
I see the point. I'm just a bit concerned about the fact there will be two same
artifacts which are just published in different way. There could be a the trouble to
understand why there are two and what's the difference. I understand the fact about
the maven dependecy and ease of handling for the jar.
Ok, then from what was discussed here I agree that we need to have two artifact being
published.
The only other minor thing which came to my mind if we need to have two separate maven
modules or this will be just in one.
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)