[jbossts-issues] [JBoss JIRA] (JBTM-3293) LRA coordinator jar cannot be deployed on WildFly

[Martin Stefanko (Jira)]

    [ https://issues.redhat.com/browse/JBTM-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14049060#comment-14049060 ] 

Martin Stefanko edited comment on JBTM-3293 at 4/21/20 9:56 AM:
----------------------------------------------------------------

The jar artifact can still be consumed in other runtimes/user applications if they want to do so I would strongly suggest keeping publishing this artifact. 

The war module I proposed makes sense only for WFLY deployments. I haven't tested other similar runtimes. But this issue was about deploying this artifact to the wildfly server. A user can do the same add a lra-coordinator-jar dependency to their war archive together with narayana-lra dependency and a bunch of other dependencies they may need. In my experience I've never added war packaged maven dependency so I don't know what are the correct guidelines here but I personally would prefer to have both lra-coordinator-jar and lra-coodinator-war modules.


was (Author: mstefank):
The jar artifact can still be consumed in other runtimes/user applications if they want to so I would strongly suggest keeping publishing this artifact. 

The war module I proposed makes sense only for WFLY deployments. I haven't tested other similar runtimes. But this issue was about deploying this artifact to the wildfly server. A user can do the same add a lra-coordinator-jar dependency to their war archive together with narayana-lra dependency and a bunch of other dependencies they may need. In my experience I've never added war packaged maven dependency so I don't know what are the correct guidelines here but I personally would prefer to have both lra-coordinator-jar and lra-coodinator-war modules.

> 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)