[jbossts-issues] [JBoss JIRA] (JBTM-3126) @LRA may begin a nested LRA without the presence of @NestedLRA

[Michael Musgrove (Jira)]

     [ https://issues.jboss.org/browse/JBTM-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Musgrove updated JBTM-3126:
-----------------------------------
        Status: Resolved  (was: Pull Request Sent)
    Resolution: Done


> @LRA may begin a nested LRA without the presence of @NestedLRA 
> ---------------------------------------------------------------
>
>                 Key: JBTM-3126
>                 URL: https://issues.jboss.org/browse/JBTM-3126
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: LRA
>    Affects Versions: 5.9.5.Final
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>            Priority: Major
>             Fix For: 5.next
>
>
> If a JAX-RS method is invoked and the following conditions are met:
> - the invoked method is annotated with LRA.Type.REQUIRES_NEW;
> - the invoked method is not annotated with @Nested;
> - there is an LRA context present on the incoming request
> then the implementation (of the LRA spec) will begin a nested LRA which is contrary to the specified behaviour. Note that there is an [outstanding issue regarding nested LRAs|https://github.com/eclipse/microprofile-lra/issues/117] but this issue affects the implementation of the current specification and needs fixing.
> In addition there is also the situation where the outbound JAX-RS request filter may override  the LRA context header (this issue can be reproduced by starting an LRA and then starting a JAX-RS request with a different "LRA context header" - the expected behaviour in this case is to run the request with the context set by the user.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)