October 2017 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2938) LRA participant complete/compensate methods should use HTTP PUT

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2938?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2938: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1227 > LRA participant complete/compensate methods should use HTTP PUT > --------------------------------------------------------------- > > Key: JBTM-2938 > URL: https://issues.jboss.org/browse/JBTM-2938 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.7.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > LRA participant complete and compensate methods are currently called using an HTTP POST request. Since these methods should be idempotent they should respond to PUT since in a REST based system PUT is idempotent and POST is not. > Both the implementation and the specification need changing. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2937) Do not recommend "X-" prefixed headers

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2937?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2937: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Resolved by PR https://github.com/jbosstm/narayana/pull/1227 > Do not recommend "X-" prefixed headers > -------------------------------------- > > Key: JBTM-2937 > URL: https://issues.jboss.org/browse/JBTM-2937 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: LRA > Affects Versions: 5.7.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > Quote from PR https://github.com/jbosstm/microprofile-sandbox/pull/3 raised by @nicolaferraro : > {quote} > A small change to the spec in order to use "Long-Running-Action" and "Short-Running-Action" headers instead of "X-lra" and "X-sra". > "X-" prefixed headers should be deprecated by RFC-6648 and RFC-7231. > They are not mandated by this spec, but they'll be used by microprofile rest services, so it's important for other technologies to use them if they want to build interoperable rest services. > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2940) LRA participant complete/compensate endpoints should be allowed to return a 202 Accepted HTTP status

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2940?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2940: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > LRA participant complete/compensate endpoints should be allowed to return a 202 Accepted HTTP status > ---------------------------------------------------------------------------------------------------- > > Key: JBTM-2940 > URL: https://issues.jboss.org/browse/JBTM-2940 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: LRA > Affects Versions: 5.7.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The compensate and complete participant endpoints are allowed to return `202 Accepted` if they cannot complete the operation immediately in which case they should either return a status URL in the HTTP Location Header of the response or the resource class should contain a method annotated with @Status. > Recovery should then periodically probe the status and clean up once the status indicates that the participant has completed or compensated. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2942) LRA tests failed when building with the JDK9

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2942?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2942: -------------------------------- Labels: jdk9 (was: ) > LRA tests failed when building with the JDK9 > -------------------------------------------- > > Key: JBTM-2942 > URL: https://issues.jboss.org/browse/JBTM-2942 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.7.0.Final > Reporter: Amos Feng > Assignee: Amos Feng > Labels: jdk9 > > The lra-test still failed with java.lang.IllegalArgumentException when deploying the war. It looks like the wildfly-swarm does support the JDK9 currently. Also I find 1 and 2 with the same issues. > 1. https://stackoverflow.com/questions/46449735/wildfly-swarm-deployment-cra... > 2. https://stackoverflow.com/questions/42990017/illegalargumentexception-whi... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2941) Support JAX-RS unaware LRA participants

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2941?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Michael Musgrove created pull request #1228 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Support JAX-RS unaware LRA participants > --------------------------------------- > > Key: JBTM-2941 > URL: https://issues.jboss.org/browse/JBTM-2941 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: LRA > Affects Versions: 5.7.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The LRA proposal includes a Java based compensation registration API to support those applications that cannot directly expose JAX-RS endpoints for compensation activities. This JIRA adds a reference implementation of that API. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2942) LRA tests failed when building with the JDK9

by Amos Feng (JIRA)

Amos Feng created JBTM-2942: ------------------------------- Summary: LRA tests failed when building with the JDK9 Key: JBTM-2942 URL: https://issues.jboss.org/browse/JBTM-2942 Project: JBoss Transaction Manager Issue Type: Bug Components: LRA Affects Versions: 5.7.0.Final Reporter: Amos Feng Assignee: Amos Feng The lra-test still failed with java.lang.IllegalArgumentException when deploying the war. It looks like the wildfly-swarm does support the JDK9 currently. Also I find 1 and 2 with the same issues. 1. https://stackoverflow.com/questions/46449735/wildfly-swarm-deployment-cra... 2. https://stackoverflow.com/questions/42990017/illegalargumentexception-whi... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2941) Support JAX-RS unaware LRA participants

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2941: -------------------------------------- Summary: Support JAX-RS unaware LRA participants Key: JBTM-2941 URL: https://issues.jboss.org/browse/JBTM-2941 Project: JBoss Transaction Manager Issue Type: Enhancement Components: LRA Affects Versions: 5.7.0.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next The LRA proposal includes a Java based compensation registration API to support those applications that cannot directly expose JAX-RS endpoints for compensation activities. This JIRA adds a reference implementation of that API. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2940) LRA participant complete/compensate endpoints should be allowed to return a 202 Accepted HTTP status

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2940?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Michael Musgrove created pull request #1227 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > LRA participant complete/compensate endpoints should be allowed to return a 202 Accepted HTTP status > ---------------------------------------------------------------------------------------------------- > > Key: JBTM-2940 > URL: https://issues.jboss.org/browse/JBTM-2940 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: LRA > Affects Versions: 5.7.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The compensate and complete participant endpoints are allowed to return `202 Accepted` if they cannot complete the operation immediately in which case they should either return a status URL in the HTTP Location Header of the response or the resource class should contain a method annotated with @Status. > Recovery should then periodically probe the status and clean up once the status indicates that the participant has completed or compensated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2937) Do not recommend "X-" prefixed headers

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2937?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Michael Musgrove created pull request #1226 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Do not recommend "X-" prefixed headers > -------------------------------------- > > Key: JBTM-2937 > URL: https://issues.jboss.org/browse/JBTM-2937 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: LRA > Affects Versions: 5.7.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > Quote from PR https://github.com/jbosstm/microprofile-sandbox/pull/3 raised by @nicolaferraro : > {quote} > A small change to the spec in order to use "Long-Running-Action" and "Short-Running-Action" headers instead of "X-lra" and "X-sra". > "X-" prefixed headers should be deprecated by RFC-6648 and RFC-7231. > They are not mandated by this spec, but they'll be used by microprofile rest services, so it's important for other technologies to use them if they want to build interoperable rest services. > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2940) LRA participant complete/compensate endpoints should be allowed to return a 202 Accepted HTTP status

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2940: -------------------------------------- Summary: LRA participant complete/compensate endpoints should be allowed to return a 202 Accepted HTTP status Key: JBTM-2940 URL: https://issues.jboss.org/browse/JBTM-2940 Project: JBoss Transaction Manager Issue Type: Enhancement Components: LRA Affects Versions: 5.7.0.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next The compensate and complete participant endpoints are allowed to return `202 Accepted` if they cannot complete the operation immediately in which case they should either return a status URL in the HTTP Location Header of the response or the resource class should contain a method annotated with @Status. Recovery should then periodically probe the status and clean up once the status indicates that the participant has completed or compensated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues October 2017