November 2014 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1759) Update the OTS related IDL files

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1759?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-1759: ----------------------------------- Removed DRAFT3. That's dating back to 1991 and all ORBs we're using today should not be impacted by this. > Update the OTS related IDL files > -------------------------------- > > Key: JBTM-1759 > URL: https://issues.jboss.org/browse/JBTM-1759 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Mark Little > > CosTSInterop and CosTSInterop as well. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1759) Update the OTS related IDL files

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1759?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-1759: ----------------------------------- Updated CosTSInteroperation.idl for not. However, we should be getting to a point where we can use the CosTransactions.idl and friends provided by the ORB we're using. That's always been the goal. > Update the OTS related IDL files > -------------------------------- > > Key: JBTM-1759 > URL: https://issues.jboss.org/browse/JBTM-1759 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Mark Little > > CosTSInterop and CosTSInterop as well. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2299) Why does Blacktie have its own CosTransactions.idl?

by Mark Little (JIRA)

Mark Little created JBTM-2299: --------------------------------- Summary: Why does Blacktie have its own CosTransactions.idl? Key: JBTM-2299 URL: https://issues.jboss.org/browse/JBTM-2299 Project: JBoss Transaction Manager Issue Type: Task Components: BlackTie Affects Versions: 5.0.3 Reporter: Mark Little Assignee: Amos Feng Shouldn't it use the one in ArjunaJTS? -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-185) Check POA attributes

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-185?page=com.atlassian.jira.plugin.s... ] Mark Little resolved JBTM-185. ------------------------------ Resolution: Out of Date > Check POA attributes > -------------------- > > Key: JBTM-185 > URL: https://issues.jboss.org/browse/JBTM-185 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Reporter: Mark Little > Assignee: Mark Little > > Check use of POA attribute for transaction context propagation in interceptors. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-185) Check POA attributes

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-185?page=com.atlassian.jira.plugin.s... ] Mark Little closed JBTM-185. ---------------------------- > Check POA attributes > -------------------- > > Key: JBTM-185 > URL: https://issues.jboss.org/browse/JBTM-185 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Reporter: Mark Little > Assignee: Mark Little > > Check use of POA attribute for transaction context propagation in interceptors. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2122) Go through JTS code and compare/contrast with capabilities missing in other dist tx code we've got

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-2122?page=com.atlassian.jira.plugin.... ] Mark Little updated JBTM-2122: ------------------------------ Summary: Go through JTS code and compare/contrast with capabilities missing in other dist tx code we've got (was: Go through JTS code and compare/contrast with capabilities missing in other diet tx code we've got) > Go through JTS code and compare/contrast with capabilities missing in other dist tx code we've got > -------------------------------------------------------------------------------------------------- > > Key: JBTM-2122 > URL: https://issues.jboss.org/browse/JBTM-2122 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Affects Versions: 5.0.1 > Reporter: Mark Little > Assignee: Mark Little > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-223) Check WL-to-JBossTS interoperability (via JTS).

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-223?page=com.atlassian.jira.plugin.s... ] Mark Little updated JBTM-223: ----------------------------- Assignee: (was: Mark Little) > Check WL-to-JBossTS interoperability (via JTS). > ----------------------------------------------- > > Key: JBTM-223 > URL: https://issues.jboss.org/browse/JBTM-223 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Reporter: Mark Little > Fix For: 6.0.0 > > > Extensible header structure corba call > key value slot ids > slot for transaction context is not in the well known slot > tx context was not defined so we used the market leader at the time -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1605) Integrate STM with vert.x

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1605?page=com.atlassian.jira.plugin.... ] Mark Little closed JBTM-1605. ----------------------------- > Integrate STM with vert.x > ------------------------- > > Key: JBTM-1605 > URL: https://issues.jboss.org/browse/JBTM-1605 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: STM > Affects Versions: 5.0.0.M2 > Reporter: Mark Little > Assignee: Mark Little > > Finish the work started last year. Actor+transaction model. > Due to the typical way vert.x works (one thread per task, unique classloader instance etc.), shared state is typically not a concern even between threads. STM still useful to ensure atomic updates in the presence of failures, or sharing via message passing. However, with our STM implementation, persistent instances can be shared between threads or processes in different address spaces if needed. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1605) Integrate STM with vert.x

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1605?page=com.atlassian.jira.plugin.... ] Mark Little resolved JBTM-1605. ------------------------------- Resolution: Done Done for now. Details published to Vert.x group a few months back. Waiting on further feedback before doing more. > Integrate STM with vert.x > ------------------------- > > Key: JBTM-1605 > URL: https://issues.jboss.org/browse/JBTM-1605 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: STM > Affects Versions: 5.0.0.M2 > Reporter: Mark Little > Assignee: Mark Little > > Finish the work started last year. Actor+transaction model. > Due to the typical way vert.x works (one thread per task, unique classloader instance etc.), shared state is typically not a concern even between threads. STM still useful to ensure atomic updates in the presence of failures, or sharing via message passing. However, with our STM implementation, persistent instances can be shared between threads or processes in different address spaces if needed. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2298) Use Project Atomic for docker image(s)

by Mark Little (JIRA)

Mark Little created JBTM-2298: --------------------------------- Summary: Use Project Atomic for docker image(s) Key: JBTM-2298 URL: https://issues.jboss.org/browse/JBTM-2298 Project: JBoss Transaction Manager Issue Type: Task Components: JTS, REST, XTS Affects Versions: 5.0.3 Reporter: Mark Little Assignee: Michael Musgrove When I created the initial docker (POC) image I did so using a standard Fedora base image. We should also look at supporting the Project Atomic docker image, since it's important for Red Hat. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues November 2014