[
https://issues.jboss.org/browse/JBTM-2449?page=com.atlassian.jira.plugin....
]
Michael Musgrove commented on JBTM-2449:
----------------------------------------
The problem is that we do not have a separate project for the SPI and we use a narayana
JIRA for tracking SPI changes. But sometimes (although rarely) we release the SPI for
projects other than narayana (this JIRA is such an example).
The fix went into jboss-transaction:7.3.3.Final and the first narayana release that
consumed that version was 5.3.5.Final so I an option would be to use that as the fix
version field.
SPI class ServerVMClientUserTransaction should be Serializable and
Referenceable
--------------------------------------------------------------------------------
Key: JBTM-2449
URL:
https://issues.jboss.org/browse/JBTM-2449
Project: JBoss Transaction Manager
Issue Type: Bug
Components: SPI
Affects Versions: 5.1.1
Reporter: Michael Musgrove
Assignee: Michael Musgrove
Fix For: 5.2.0
This SPI class implements UserTransaction but does not follow the JNDI conventions. The
JTA specification (section 3.1) says:
bq. The implementation of the UserTransaction object must be both
javax.naming.Referenceable and java.io.Serializable , so that the object can be stored in
all JNDI naming contexts.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)