[jbossts-issues] [JBoss JIRA] (JBTM-3232) Conflicting JAX-RS paths in io.narayana.lra.coordinator.api.Coordinator

Michael Musgrove (Jira) issues at jboss.org
Tue Dec 10 11:06:00 EST 2019


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

Michael Musgrove commented on JBTM-3232:
----------------------------------------

Just delete the nested path (and move the code into the other endpoint).

> Conflicting JAX-RS paths in io.narayana.lra.coordinator.api.Coordinator
> -----------------------------------------------------------------------
>
>                 Key: JBTM-3232
>                 URL: https://issues.redhat.com/browse/JBTM-3232
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: LRA
>    Affects Versions: 5.10.1.Final
>            Reporter: Martin Stefanko
>            Assignee: Martin Stefanko
>            Priority: Major
>
> In the JAX-RS resource io.narayana.lra.coordinator.api.Coordinator there are two conflicting JAX-RS paths:
> {code:java}
> @GET
> @Path("{LraId}/status")
> public Response getLRAStatus 
> {code}
> and 
> {code:java}
> @GET
> @Path("{NestedLraId}/status")
> public Response getNestedLRAStatus
> {code}
> which impose erroneous states for the nested LRAs. I would propose to prefix all endpoints for nested LRAs at the Coordinator class to be prefixed with `/nested`.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)


More information about the jbossts-issues mailing list