[jbossts-issues] [JBoss JIRA] (JBTM-3225) Decide whether we should make the internal LRA client API not auto closable

[Michael Musgrove (Jira)]

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

Michael Musgrove updated JBTM-3225:
-----------------------------------
    Fix Version/s: 5.next
                       (was: 5.10.2.Final)


> Decide whether we should make the internal LRA client API not auto closable
> ---------------------------------------------------------------------------
>
>                 Key: JBTM-3225
>                 URL: https://issues.redhat.com/browse/JBTM-3225
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>          Components: LRA
>    Affects Versions: 5.10.0.Final
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>            Priority: Major
>             Fix For: 5.next
>
>
> The LRA implementation contains an internal client API called io.narayana.lra.client.NarayanaLRAClient which implements java.io.Closeable. A recent PR (see issue https://issues.jboss.org/browse/JBTM-3212) made the implementation of the close method a NOOP (since there is no longer any need for cleanup actions). But the method was left empty since there is a possibility that is will be needed in LRA version 1.x where a LRA client API will be added and since there are existing users of the client API.
> This task is a reminder to revisit the decision to remove java.io.Closeable prior to releasing an implementation of [version 1.0 of the LRA specification|https://github.com/eclipse/microprofile-lra/issues?q=is%3Aopen+is%3Aissue+milestone%3A1.0].
>  



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