jbossts-issues

jbossts-issues@lists.jboss.org
  • 1 participants
  • 69 discussions
[JBoss JIRA] (JBTM-2957) LRA specification: descriptions for start/end and LRA do not say which response codes are valid
by Michael Musgrove (JIRA)
3 years, 2 months
[JBoss JIRA] (JBTM-2959) Allow different LRA coordinators to share an object store
by Michael Musgrove (JIRA)
3 years, 2 months
[JBoss JIRA] (JBTM-2957) LRA spec start and finish descriptions do not specify HTTP status codes
by Michael Musgrove (JIRA)
3 years, 2 months
[JBoss JIRA] (JBTM-2958) Wrong format of the Link header on joining LRA by participant should return error to the participant
by Ondra Chaloupka (JIRA)
3 years, 2 months
[JBoss JIRA] (JBTM-2957) LRA spec start and finish descriptions do not specify HTTP status codes
by Michael Musgrove (JIRA)
3 years, 2 months
[JBoss JIRA] (JBTM-2954) LRA coordinator REST endpoint is ambiguous if no Accept header is defined and for noContent is http status 204
by Ondra Chaloupka (JIRA)
3 years, 2 months
[JBoss JIRA] (JBTM-2954) LRA coordinator REST endpoint is ambiguous if no Accept header is defined and for noContent is http status 204
by Ondra Chaloupka (JIRA)
3 years, 2 months
[JBoss JIRA] (JBTM-2954) LRA coordinator REST endpoint is ambiguous if no Accept header is defined and for noContent is http status 204
by Ondra Chaloupka (JIRA)
3 years, 2 months
[JBoss JIRA] (JBTM-2954) LRA coordinator REST endpoint is ambiguous if no Accept header is defined and for noContent is http status 204
by Ondra Chaloupka (JIRA)
3 years, 2 months
[JBoss JIRA] (JBTM-2954) LRA coordinator REST endpoint is ambiguous if no Accept header is defined and for noContent is http status 204
by Michael Musgrove (JIRA)
3 years, 2 months
Results per page: