[jbossts-issues] [JBoss JIRA] (JBTM-2957) LRA spec start and finish descriptions do not specify HTTP status codes
Michael Musgrove (JIRA)
issues at jboss.org
Mon Nov 13 08:19:00 EST 2017
[ https://issues.jboss.org/browse/JBTM-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13489335#comment-13489335 ]
Michael Musgrove commented on JBTM-2957:
----------------------------------------
Both LRA and LRA participant lifecycle operations need to support asynchronicity (ie 202 Accepted response status codes should be valid).
> LRA spec start and finish descriptions do not specify HTTP status codes
> -----------------------------------------------------------------------
>
> Key: JBTM-2957
> URL: https://issues.jboss.org/browse/JBTM-2957
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Components: LRA
> Affects Versions: 5.7.1.Final
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 5.later
>
>
> The specification does not specify the HTTP response codes for starting and ending LRAs. The [relevant sections of the specification|https://github.com/eclipse/microprofile-sandbox/blob/master/proposals/0009-LRA/README.md#protocol-urls] are:
> > Performing a `POST` on ... creates an LRA.
> > Performing a `PUT` on .../close will trigger the successful completion of the LRA ...
> This means that it is vague as to whether asynchronous operations are supported, which they should be (since the target use case for LRAs is a microservice based environment).
> The proposal should be updated to include the response codes and it SHOULD include the ability to return "202 Accepted"
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the jbossts-issues
mailing list