September 2019 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3187) Add MessageBodyWriter for ParticipantStatus and application/octet-stream media type

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3187?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3187: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add MessageBodyWriter for ParticipantStatus and application/octet-stream media type > ----------------------------------------------------------------------------------- > > Key: JBTM-3187 > URL: https://issues.jboss.org/browse/JBTM-3187 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: LRA > Affects Versions: 5.9.8.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > application/octet-stream is the default media type in RESTEasy which is used when {{@Produces}} value is not specified. We are always expecting {{String}} values from LRA participant methods so instead of requiring {{(a)Produces(MediaType.TEXT_PLAIN)}} on each {{@Compensate}}, {{@Complete}}, {{@Status}}, etc. methods we can include {{MessageBodyWriter<ParticipantStatus>}} implementation in {{narayana-lra}} module which will just transform {{ParticipantStatus}} value to {{String}}. -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3187) Add MessageBodyWriter for ParticipantStatus and application/octet-stream media type

by Anonymous (Jira)

[ https://issues.jboss.org/browse/JBTM-3187?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Martin Stefanko created pull request #1496 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Add MessageBodyWriter for ParticipantStatus and application/octet-stream media type > ----------------------------------------------------------------------------------- > > Key: JBTM-3187 > URL: https://issues.jboss.org/browse/JBTM-3187 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: LRA > Affects Versions: 5.9.8.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > application/octet-stream is the default media type in RESTEasy which is used when {{@Produces}} value is not specified. We are always expecting {{String}} values from LRA participant methods so instead of requiring {{(a)Produces(MediaType.TEXT_PLAIN)}} on each {{@Compensate}}, {{@Complete}}, {{@Status}}, etc. methods we can include {{MessageBodyWriter<ParticipantStatus>}} implementation in {{narayana-lra}} module which will just transform {{ParticipantStatus}} value to {{String}}. -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3187) Add MessageBodyWriter for ParticipantStatus and application/octet-stream media type

by Martin Stefanko (Jira)

Martin Stefanko created JBTM-3187: ------------------------------------- Summary: Add MessageBodyWriter for ParticipantStatus and application/octet-stream media type Key: JBTM-3187 URL: https://issues.jboss.org/browse/JBTM-3187 Project: JBoss Transaction Manager Issue Type: Enhancement Components: LRA Affects Versions: 5.9.8.Final Reporter: Martin Stefanko Assignee: Martin Stefanko application/octet-stream is the default media type in RESTEasy which is used when {{@Produces}} value is not specified. We are always expecting {{String}} values from LRA participant methods so instead of requiring {{(a)Produces(MediaType.TEXT_PLAIN)}} on each {{@Compensate}}, {{@Complete}}, {{@Status}}, etc. methods we can include {{MessageBodyWriter<ParticipantStatus>}} implementation in {{narayana-lra}} module which will just transform {{ParticipantStatus}} value to {{String}}. -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3182) Fix basic LRA tests

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3182?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3182: ----------------------------------- Fix Version/s: 5.9.8.Final > Fix basic LRA tests > ------------------- > > Key: JBTM-3182 > URL: https://issues.jboss.org/browse/JBTM-3182 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.7.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > Fix For: 5.9.8.Final > > > lra-test/basic is unable to run because of wrong CDI configuration after latest LRA upgrade: > {code:java} > ERROR [org.jboss.resteasy.resteasy_jaxrs.i18n] (default task-1) RESTEASY002025: Unknown exception while executing GET /root/participant/lra: java.lang.NullPointerException > at io.narayana.lra.filter.ServerLRAFilter.filter(ServerLRAFilter.java:311) > {code} -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3186) Safeguard LRA filters for situations when CDI is not available

by Martin Stefanko (Jira)

[ https://issues.jboss.org/browse/JBTM-3186?page=com.atlassian.jira.plugin.... ] Martin Stefanko updated JBTM-3186: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1495 > Safeguard LRA filters for situations when CDI is not available > --------------------------------------------------------------- > > Key: JBTM-3186 > URL: https://issues.jboss.org/browse/JBTM-3186 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > When CDI is not available in LRA microservice, following exception is thrown: > {code:java} > Caused by: java.lang.NullPointerException > at io.narayana.lra.filter.ServerLRAFilter.filter(ServerLRAFilter.java:311) > {code} > This is thrown because CDI is not available in the container. The check for null injection can prohibit this behavior and LRA can still function for REST-based services in case CDI is not present. -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3186) Safeguard LRA filters for situations when CDI is not available

by Martin Stefanko (Jira)

[ https://issues.jboss.org/browse/JBTM-3186?page=com.atlassian.jira.plugin.... ] Martin Stefanko updated JBTM-3186: ---------------------------------- Description: When CDI is not available in LRA microservice, following exception is thrown: {code:java} Caused by: java.lang.NullPointerException at io.narayana.lra.filter.ServerLRAFilter.filter(ServerLRAFilter.java:311) {code} This is thrown because CDI is not available in the container. The check for null injection can prohibit this behavior and LRA can still function for REST-based services in case CDI is not present. was: When CDI is not available in LRA microservice, following exception is thrown: ``` Caused by: java.lang.NullPointerException at io.narayana.lra.filter.ServerLRAFilter.filter(ServerLRAFilter.java:311) ``` This is thrown because CDI is not available in the container. The check for null injection can prohibit this behavior and LRA can still function for REST-based services in case CDI is not present. > Safeguard LRA filters for situations when CDI is not available > --------------------------------------------------------------- > > Key: JBTM-3186 > URL: https://issues.jboss.org/browse/JBTM-3186 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > When CDI is not available in LRA microservice, following exception is thrown: > {code:java} > Caused by: java.lang.NullPointerException > at io.narayana.lra.filter.ServerLRAFilter.filter(ServerLRAFilter.java:311) > {code} > This is thrown because CDI is not available in the container. The check for null injection can prohibit this behavior and LRA can still function for REST-based services in case CDI is not present. -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3186) Safeguard LRA filters for situations when CDI is not available

by Martin Stefanko (Jira)

Martin Stefanko created JBTM-3186: ------------------------------------- Summary: Safeguard LRA filters for situations when CDI is not available Key: JBTM-3186 URL: https://issues.jboss.org/browse/JBTM-3186 Project: JBoss Transaction Manager Issue Type: Bug Components: LRA Reporter: Martin Stefanko Assignee: Martin Stefanko When CDI is not available in LRA microservice, following exception is thrown: ``` Caused by: java.lang.NullPointerException at io.narayana.lra.filter.ServerLRAFilter.filter(ServerLRAFilter.java:311) ``` This is thrown because CDI is not available in the container. The check for null injection can prohibit this behavior and LRA can still function for REST-based services in case CDI is not present. -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3180) LRARecord http compliance: Entity null for PUT

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3180?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Michael Musgrove created pull request #1494 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > LRARecord http compliance: Entity null for PUT > ---------------------------------------------- > > Key: JBTM-3180 > URL: https://issues.jboss.org/browse/JBTM-3180 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.7.Final > Reporter: Paul Parkinson > Assignee: Michael Musgrove > Priority: Minor > > LRARecord has... > case "javax.ws.rs.PUT": > return asyncInvoker.put(Entity.text(null)); > whereas entity should never be null for PUT > I see this comment has been there since the code was first added and so perhaps this is the desired... > // return asyncInvoker.put(Entity.entity(compensatorData, mediaType)); > If not perhaps simply Entity.text("") should suffice (and has in my tests). -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2912) Upgrade JMS transactional driver to JMS 2.0

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-2912?page=com.atlassian.jira.plugin.... ] Ondrej Chaloupka updated JBTM-2912: ----------------------------------- Status: Open (was: Pull Request Sent) > Upgrade JMS transactional driver to JMS 2.0 > ------------------------------------------- > > Key: JBTM-2912 > URL: https://issues.jboss.org/browse/JBTM-2912 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JMS > Reporter: Thomas Jenkinson > Priority: Major > Fix For: 5.next > > > The transactional driver was implemented for JMS API 1.1. We should upgrade to 2.0. -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3181) lra-proxy-api is not deployed to Nexus during release

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3181?page=com.atlassian.jira.plugin.... ] Ondrej Chaloupka updated JBTM-3181: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 5.9.8.Final (was: 5.next) Resolution: Done > lra-proxy-api is not deployed to Nexus during release > ----------------------------------------------------- > > Key: JBTM-3181 > URL: https://issues.jboss.org/browse/JBTM-3181 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.7.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > Fix For: 5.9.8.Final > > > Artifact `lra-proxy-api` is not (and it has never been) deployed at Nexus. -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 7 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 September 2019