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

[Michael Musgrove (Jira)]

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

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

In fact the code should be identical with the other status endpoint so just delete it.
The other endpoints with the NestedLraId param should not cause any issues so they can be left as they are.

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