Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-3767

LRA API versioning scheme is too restrictive

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Done
    • Icon: Major Major
    • 6.0.1.Final
    • 6.0.0.Final
    • LRA
    • None
    • Fix an issue that stops later versions of the client from working with earlier versions of the coordinator

      The LRA API version scheme seems to only support the latest version:

      21:09:47 WARN  [io.na.lra] (executor-thread-1) LRA025014: reason 'WebApplicationException null: LRA025001: LRA created with an unexpected status code: 417, coordinator response 'LRA025028: Demanded API version '1.1' is not in the list of the supported versions '[Ljava.lang.String;@4797d38c'. Please, provide the right version for the API.'': container request for method 'org.acme.quickstart.lra.coordinator.TransactionalResource#startTx': lra: 'context'
      21:09:47 WARN  [io.na.lra] (executor-thread-1) LRA025025: Unable to process LRA annotations: -3: StartFailed (null: LRA025001: LRA created with an unexpected status code: 417, coordinator response 'LRA025028: Demanded API version '1.1' is not in the list of the supported versions '[Ljava.lang.String;@4797d38c'. Please, provide the right version for the API.') ()'

       

      It needs updating so that it is more fine grained. So in the example above the request can be serviced with the current code base using any version of the API.

            rh-ee-msappegr Marco Sappe Griot
            rhn-engineering-mmusgrov Michael Musgrove
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: