November 2014 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2238) Tooling does not expose CMR records

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2238?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2238: ----------------------------------------------- Hayk Hovsepyan <hhovsepy(a)redhat.com> changed the Status of [bug 1113225|https://bugzilla.redhat.com/show_bug.cgi?id=1113225] from POST to VERIFIED > Tooling does not expose CMR records > ----------------------------------- > > Key: JBTM-2238 > URL: https://issues.jboss.org/browse/JBTM-2238 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.22, 5.0.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.23, 5.0.3 > > > CMR resources are not being exposed as MBeans via the (com.arjuna.ats.arjuna.tools.osb.mbean.ObjStoreBrowser) tooling. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2283) Tooling no longer exposes JTS record types

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2283?page=com.atlassian.jira.plugin.... ] Michael Musgrove edited comment on JBTM-2283 at 11/7/14 5:02 AM: ----------------------------------------------------------------- I normally do do good descriptions but in this case the bugzilla said it all. But I hear what you are saying and a precis of the linked bugzilla would have helped here to keep the JIRA self contained. was (Author: mmusgrov): I normally do do good descriptions but in this case the bugzilla said it all. But I hear what you are saying and a precis of the linked bugzilla would have helped here to keep the JIRA self contained. Mike -- Michael Musgrove Transactions Team e: mmusgrov(a)redhat.com t: +44 191 243 0870 Registered in England and Wales under Company Registration No. 03798903 Directors: Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Michael O'Neill(Ireland) > Tooling no longer exposes JTS record types > ------------------------------------------ > > Key: JBTM-2283 > URL: https://issues.jboss.org/browse/JBTM-2283 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.4 > > > Transacton records of type StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple are no longer exposed via the tooling. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2283) Tooling no longer exposes JTS record types

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2283?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-2283: ---------------------------------------- I normally do do good descriptions but in this case the bugzilla said it all. But I hear what you are saying and a precis of the linked bugzilla would have helped here to keep the JIRA self contained. Mike -- Michael Musgrove Transactions Team e: mmusgrov(a)redhat.com t: +44 191 243 0870 Registered in England and Wales under Company Registration No. 03798903 Directors: Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Michael O'Neill(Ireland) > Tooling no longer exposes JTS record types > ------------------------------------------ > > Key: JBTM-2283 > URL: https://issues.jboss.org/browse/JBTM-2283 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.4 > > > Transacton records of type StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple are no longer exposed via the tooling. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2283) Tooling no longer exposes JTS record types

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-2283?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-2283: ----------------------------------- Thanks. That's a much better description and makes it easier for people in the future to understand what you were doing. Unless a JIRA title is really self explanatory (this one isn't) let's keep the Description field as informative as possible (this one wasn't). > Tooling no longer exposes JTS record types > ------------------------------------------ > > Key: JBTM-2283 > URL: https://issues.jboss.org/browse/JBTM-2283 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.4 > > > Transacton records of type StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple are no longer exposed via the tooling. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2283) Tooling no longer exposes JTS record types

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2283?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-2283: ---------------------------------------- The tooling maintained a map between record types and type names. Then, for each record type there is a bean that is responsible for exposing info about an instance of that record type (another map). To simplify things I condensed the two maps to a collection of tuples (record type, bean type, typename). When I did the refactor I lost the typename for JTS record types. I fixed that and added a test to catch any further oversights. > Tooling no longer exposes JTS record types > ------------------------------------------ > > Key: JBTM-2283 > URL: https://issues.jboss.org/browse/JBTM-2283 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.4 > > > Transacton records of type StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple are no longer exposed via the tooling. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2283) Tooling no longer exposes JTS record types

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-2283?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-2283: ----------------------------------- Can you expand on this JIRA to say why they're no longer exposed ;-) ? > Tooling no longer exposes JTS record types > ------------------------------------------ > > Key: JBTM-2283 > URL: https://issues.jboss.org/browse/JBTM-2283 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.4 > > > Transacton records of type StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple are no longer exposed via the tooling. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2280) alternative to JNDI

by SBS JIRA Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2280?page=com.atlassian.jira.plugin.... ] SBS JIRA Integration updated JBTM-2280: --------------------------------------- Forum Reference: https://developer.jboss.org/message/909177#909177 > alternative to JNDI > ------------------- > > Key: JBTM-2280 > URL: https://issues.jboss.org/browse/JBTM-2280 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Gavin King > Assignee: Tom Jenkinson > > So far four (4) different people have tried and failed to get JBoss Transactions working in a Ceylon environment (i.e. JBoss Modules, essentially). The basic problem is that the TM has a totally spurious dependence on JNDI as the source of its transactional resources. Since JCA is neither defined nor available outside a Java EE environment, this forces anyone trying to use the TM outside of the application server to write their own nasty code depending on some really internal-looking APIs that basically sets up a JNDI-bound proxied datasource where both the TM and the application can find it. In principle this is sorta-straightforward (except for the internal-looking APIs). However, it means that most of the code in `ceylon.transaction` is actually about connection management and setting up JNDI-bound datasources. > Sadly it turns out that, in the context of JBoss Modules, even just getting a JNDI server on the right classloader has proved to be a task so difficult that four reasonably competent developers including myself and other folks who are much better programmers than me have failed at it. I'm sure it's remotely _possible_, and I'm sure that if I weren't using JBoss Modules it would be quite easy. But I'm also sure that it simply shouldn't be necessary. JNDI has nothing to do with transactions and is a distraction here. JNDI is this totally stringly-typed rubbish thing designed in the Clinton era as an abstraction of LDAP by folks who had never heard that Java has static types. Yeah, sure, it continues its zombie existence at the heart of the EE standards, even after we remembered that Java has static types in EE 6, but it just has no place in modern APIs. Other libraries like Hibernate, Spring, etc always offer alternative approaches with no dependence to JNDI. > IMO, what the TM _should_ do is offer an API that lets me hand it an instance of `XADataSource` (it doesn't care where that comes from) and hands my back an instance of `DataSource` that I can use to obtain transaction-bound connections. There is no reason, AFAICT, to involve JNDI in this at all. > XADataSource xads = youJustDontNeedToCare(); > DataSource ds = narayana.registerDataSource(xads); > Or something like that. Of course I'm sure I'm missing some subtleties here. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2283) Tooling no longer exposes JTS record types

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2283?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2283: ----------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/756, https://github.com/jbosstm/narayana/pull/757 (was: https://github.com/jbosstm/narayana/pull/756) > Tooling no longer exposes JTS record types > ------------------------------------------ > > Key: JBTM-2283 > URL: https://issues.jboss.org/browse/JBTM-2283 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.4 > > > Transacton records of type StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple are no longer exposed via the tooling. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2271) ConcurrentModificationException exception raised by CMR Recovery module first pass

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2271?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2271: ----------------------------------------------- Michael <mmusgrov(a)redhat.com> changed the Status of [bug 1152782|https://bugzilla.redhat.com/show_bug.cgi?id=1152782] from NEW to ASSIGNED > ConcurrentModificationException exception raised by CMR Recovery module first pass > ---------------------------------------------------------------------------------- > > Key: JBTM-2271 > URL: https://issues.jboss.org/browse/JBTM-2271 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.3 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2280) alternative to JNDI

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2280?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-2280. --------------------------------- Resolution: Rejected Rejecting as the direct recoverable connection should work. If not, please raise a Jira/discussion against that feature. > alternative to JNDI > ------------------- > > Key: JBTM-2280 > URL: https://issues.jboss.org/browse/JBTM-2280 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Gavin King > Assignee: Tom Jenkinson > > So far four (4) different people have tried and failed to get JBoss Transactions working in a Ceylon environment (i.e. JBoss Modules, essentially). The basic problem is that the TM has a totally spurious dependence on JNDI as the source of its transactional resources. Since JCA is neither defined nor available outside a Java EE environment, this forces anyone trying to use the TM outside of the application server to write their own nasty code depending on some really internal-looking APIs that basically sets up a JNDI-bound proxied datasource where both the TM and the application can find it. In principle this is sorta-straightforward (except for the internal-looking APIs). However, it means that most of the code in `ceylon.transaction` is actually about connection management and setting up JNDI-bound datasources. > Sadly it turns out that, in the context of JBoss Modules, even just getting a JNDI server on the right classloader has proved to be a task so difficult that four reasonably competent developers including myself and other folks who are much better programmers than me have failed at it. I'm sure it's remotely _possible_, and I'm sure that if I weren't using JBoss Modules it would be quite easy. But I'm also sure that it simply shouldn't be necessary. JNDI has nothing to do with transactions and is a distraction here. JNDI is this totally stringly-typed rubbish thing designed in the Clinton era as an abstraction of LDAP by folks who had never heard that Java has static types. Yeah, sure, it continues its zombie existence at the heart of the EE standards, even after we remembered that Java has static types in EE 6, but it just has no place in modern APIs. Other libraries like Hibernate, Spring, etc always offer alternative approaches with no dependence to JNDI. > IMO, what the TM _should_ do is offer an API that lets me hand it an instance of `XADataSource` (it doesn't care where that comes from) and hands my back an instance of `DataSource` that I can use to obtain transaction-bound connections. There is no reason, AFAICT, to involve JNDI in this at all. > XADataSource xads = youJustDontNeedToCare(); > DataSource ds = narayana.registerDataSource(xads); > Or something like that. Of course I'm sure I'm missing some subtleties here. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues November 2014