[
https://issues.jboss.org/browse/JBTM-2957?page=com.atlassian.jira.plugin....
]
Michael Musgrove updated JBTM-2957:
-----------------------------------
Description:
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...]
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 (and reference implementation) should be updated to include the response
codes and it SHOULD include the ability to return "202 Accepted"
was:
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...]
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"
LRA specification: descriptions for start/end and LRA do not say
which response codes are valid
-----------------------------------------------------------------------------------------------
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...]
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 (and reference implementation) 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)