[
https://issues.jboss.org/browse/JBTM-3045?page=com.atlassian.jira.plugin....
]
Laird Nelson commented on JBTM-3045:
------------------------------------
The root cause is understood. This is not a regression.
Briefly, the JBoss {{NamingContext}} class as used indirectly by the quickstart
incorrectly expects that all {{Name}} instances supplied to, for example, {{lookup(Name)}}
be {{CompoundName}} instances. The {{TransactionExtension}} class correctly (from the
point of the JNDI specification) uses a {{CompositeName}} to lookup
{{java:/TransactionManager}}, but the JBoss {{NamingContext}} rejects it because it is not
a {{CompoundName}}.
The workaround will be for the {{TransactionExtension}} class to supply a {{String}}
("{{java:/TransactionManager}}") instead of a hand-built {{CompositeName}}.
Then non-compliant {{InitialContext}} implementations will continue to work as well as
compliant ones.
JTA CDI regression (or Standalone JTA 1.2 Quickstart failure)
-------------------------------------------------------------
Key: JBTM-3045
URL:
https://issues.jboss.org/browse/JBTM-3045
Project: JBoss Transaction Manager
Issue Type: Bug
Components: Demonstrator
Affects Versions: 5.9.0.Final
Reporter: Michael Musgrove
Priority: Critical
Fix For: 5.next
The recent changes to our JTA CDI support (
https://issues.jboss.org/browse/JBTM-3044)
have either caused a regression or the Standalone JTA 1.2 Quickstart needs updating. The
failure is:
{quote}
testMandatoryTransactionWithExistingTransaction(org.jboss.narayana.quickstarts.jta.TestCase)
Time elapsed: 0.536 sec <<< ERROR!
javax.enterprise.inject.CreationException: Not a compound name: TransactionManager
{quote}
See for example CI run
http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana-quickstarts/159/c...
If the issue does turn out to be a regression then the priority needs to be marked as
Critical.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)