January 2019 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3102) Provide a gRPC service for accessing OTS funtionality

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3102?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-3102: ---------------------------------------- The initial POC for this task is located at https://github.com/mmusgrov/narayana/tree/JBTM-3102/ArjunaJTS/grpc > Provide a gRPC service for accessing OTS funtionality > ----------------------------------------------------- > > Key: JBTM-3102 > URL: https://issues.jboss.org/browse/JBTM-3102 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Affects Versions: 5.9.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.later > > > JTS was the Java EE standard for different JTA implementations to interoperate. Since CORBA (and therefore JTS) is now an optional component of Jakarta EE there is a need for an alternative specification for how services can propagate a transaction context. A popular alternative to CORBA is gRPC which has the following nice features: 1) it is a good technology choice for service to service interactions; 2) is polyglot or, as stated in the documentation, "Automatically generates idiomatic client and server stubs for your service in a variety of languages and platforms"; and 3) provides excellent performance. > The reason JTS was chosen as the Java EE interop standard is that 1) it provides language level bindings that enable interoperability; and 2) it builds on a pre-existing industry standard, namely OTS. > Consequently, it is reasonable to conclude that a mapping from CosTransactions.idl (the IDL definition for OTS) to Protocol Buffers and gRPC services will: > - Enable existing OTS/JTS implementations to provide service in these new environments. > - Enable new and existing gRPC services to be able to access transactional functionality in an interoperable manner. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3103) LRA api-particpant quickstart needs aligning with the latest MP LRA spec changes

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3103?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Michael Musgrove created pull request #244 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > LRA api-particpant quickstart needs aligning with the latest MP LRA spec changes > -------------------------------------------------------------------------------- > > Key: JBTM-3103 > URL: https://issues.jboss.org/browse/JBTM-3103 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Michael Musgrove > Priority: Major > > This quickstart depends on LRAParticipantDeserializer to recreate participants during crash recovery but [MP LRA issue #61|https://github.com/eclipse/microprofile-lra/issues/61] has removed this class. The alternative registration mechanism is still outstanding [see the comments on issue #35|https://github.com/eclipse/microprofile-lra/issues/35] for a discussion of the new way of registering participants. > Until a PR is raised for this issue I would like to disable the quickstarts that utilise LRAParticipantDeserializer. > Note that this has only just become an issue since previouslythe Narayana implementation of LRA depended on a specific snapshot build in the eclipse repo (since the LRA spec is in flux), but snapshots are purged after a month so the old way of registering participants is no longer available. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3103) LRA api-particpant quickstart needs aligning with the latest MP LRA spec changes

by Michael Musgrove (Jira)

Michael Musgrove created JBTM-3103: -------------------------------------- Summary: LRA api-particpant quickstart needs aligning with the latest MP LRA spec changes Key: JBTM-3103 URL: https://issues.jboss.org/browse/JBTM-3103 Project: JBoss Transaction Manager Issue Type: Bug Reporter: Michael Musgrove This quickstart depends on LRAParticipantDeserializer to recreate participants during crash recovery but [MP LRA issue #61|https://github.com/eclipse/microprofile-lra/issues/61] has removed this class. The alternative registration mechanism is still outstanding [see the comments on issue #35|https://github.com/eclipse/microprofile-lra/issues/35] for a discussion of the new way of registering participants. Until a PR is raised for this issue I would like to disable the quickstarts that utilise LRAParticipantDeserializer. Note that this has only just become an issue since previouslythe Narayana implementation of LRA depended on a specific snapshot build in the eclipse repo (since the LRA spec is in flux), but snapshots are purged after a month so the old way of registering participants is no longer available. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3087) Ensure the LRA implementation is up to date

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3087?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Michael Musgrove created pull request #1401 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Reopened) > Ensure the LRA implementation is up to date > ------------------------------------------- > > Key: JBTM-3087 > URL: https://issues.jboss.org/browse/JBTM-3087 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.9.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The microprofile-lra API has undergone a number of changes recently. The narayana implementation of the specification needs updating to match the new version of it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3087) Ensure the LRA implementation is up to date

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3087?page=com.atlassian.jira.plugin.... ] Michael Musgrove reopened JBTM-3087: ------------------------------------ The Narayana implementation of LRA depends on specific snapshot builds in the eclipse repo since the LRA spec is in flux. But snapshots are purged after a month so I am reopening to bring the implementation up to date. > Ensure the LRA implementation is up to date > ------------------------------------------- > > Key: JBTM-3087 > URL: https://issues.jboss.org/browse/JBTM-3087 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.9.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The microprofile-lra API has undergone a number of changes recently. The narayana implementation of the specification needs updating to match the new version of it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3087) Ensure the LRA implementation is up to date

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3087?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3087: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Ensure the LRA implementation is up to date > ------------------------------------------- > > Key: JBTM-3087 > URL: https://issues.jboss.org/browse/JBTM-3087 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.9.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The microprofile-lra API has undergone a number of changes recently. The narayana implementation of the specification needs updating to match the new version of it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3102) Provide a gRPC service for accessing OTS funtionality

by Michael Musgrove (Jira)

Michael Musgrove created JBTM-3102: -------------------------------------- Summary: Provide a gRPC service for accessing OTS funtionality Key: JBTM-3102 URL: https://issues.jboss.org/browse/JBTM-3102 Project: JBoss Transaction Manager Issue Type: Feature Request Components: JTS Affects Versions: 5.9.2.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.later JTS was the Java EE standard for different JTA implementations to interoperate. Since CORBA (and therefore JTS) is now an optional component of Jakarta EE there is a need for an alternative specification for how services can propagate a transaction context. A popular alternative to CORBA is gRPC which has the following nice features: 1) it is a good technology choice for service to service interactions; 2) is polyglot or, as stated in the documentation, "Automatically generates idiomatic client and server stubs for your service in a variety of languages and platforms"; and 3) provides excellent performance. The reason JTS was chosen as the Java EE interop standard is that 1) it provides language level bindings that enable interoperability; and 2) it builds on a pre-existing industry standard, namely OTS. Consequently, it is reasonable to conclude that a mapping from CosTransactions.idl (the IDL definition for OTS) to Protocol Buffers and gRPC services will: - Enable existing OTS/JTS implementations to provide service in these new environments. - Enable new and existing gRPC services to be able to access transactional functionality in an interoperable manner. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3097) Small enhancement of current look and feel of narayana.io

by Ondra Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3097?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-3097: ---------------------------------- Description: Some items from the survey * announcement is pretty long - just link not 3 lines that talks the same * support of Spring is not mentioned at the page * it's hard to understand why the source code is at two places (source code goes to github and fisheye) * link for release changes for particular release could be useful * maybe a link to a logo when somebody wants to use for presentation could be added * sponsors links are not up-to-date was: Some items from the survey * announcement is pretty long - just link not 3 lines that talks the same * support of Spring is not mentioned at the page * it's hard to understand why the source code is at two places (source code goes to github and fisheye) * link for release changes for particular release could be useful * maybe a link to a logo when somebody wants to use for presentation could be added * sponsors at the page is not up-to-date > Small enhancement of current look and feel of narayana.io > --------------------------------------------------------- > > Key: JBTM-3097 > URL: https://issues.jboss.org/browse/JBTM-3097 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Reporter: Ondra Chaloupka > Priority: Major > Labels: narayana.io > > Some items from the survey > * announcement is pretty long - just link not 3 lines that talks the same > * support of Spring is not mentioned at the page > * it's hard to understand why the source code is at two places (source code goes to github and fisheye) > * link for release changes for particular release could be useful > * maybe a link to a logo when somebody wants to use for presentation could be added > * sponsors links are not up-to-date -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3101) Have a new visual design for narayana.io

by Ondra Chaloupka (Jira)

Ondra Chaloupka created JBTM-3101: ------------------------------------- Summary: Have a new visual design for narayana.io Key: JBTM-3101 URL: https://issues.jboss.org/browse/JBTM-3101 Project: JBoss Transaction Manager Issue Type: Sub-task Reporter: Ondra Chaloupka When copy-writing is done then it would be good to create a new look for the page. See e.g. * https://antora.org * https://thorntail.io * https://vertx.io * https://debezium.io -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3097) Small enhancement of current look and feel of narayana.io

by Ondra Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3097?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-3097: ---------------------------------- Description: Some items from the survey * announcement is pretty long - just link not 3 lines that talks the same * support of Spring is not mentioned at the page * it's hard to understand why the source code is at two places (source code goes to github and fisheye) * link for release changes for particular release could be useful * maybe a link to a logo when somebody wants to use for presentation could be added * sponsors at the page is not up-to-date was: Some items from the survey * announcement is pretty long - just link not 3 lines that talks the same * support of Spring is not mentioned at the page * it's hard to understand why the source code is at two places (source code goes to github and fisheye) * link for release changes for particular release could be useful * maybe a link to a logo when somebody wants to use for presentation could be added > Small enhancement of current look and feel of narayana.io > --------------------------------------------------------- > > Key: JBTM-3097 > URL: https://issues.jboss.org/browse/JBTM-3097 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Reporter: Ondra Chaloupka > Priority: Major > Labels: narayana.io > > Some items from the survey > * announcement is pretty long - just link not 3 lines that talks the same > * support of Spring is not mentioned at the page > * it's hard to understand why the source code is at two places (source code goes to github and fisheye) > * link for release changes for particular release could be useful > * maybe a link to a logo when somebody wants to use for presentation could be added > * sponsors at the page is not up-to-date -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 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 January 2019