[
https://issues.jboss.org/browse/JBTM-2460?page=com.atlassian.jira.plugin....
]
Michael Musgrove commented on JBTM-2460:
----------------------------------------
The fix relies on the transaction manager being bound into JNDI and scotts issue is a race
between his subsystem starting and jndi binding. For wildfly usage other subsystems would
use service injection (WFLY-5069 will track this)
Expose TransactionListenerRegistry via the SPI
----------------------------------------------
Key: JBTM-2460
URL:
https://issues.jboss.org/browse/JBTM-2460
Project: JBoss Transaction Manager
Issue Type: Bug
Components: SPI
Reporter: Michael Musgrove
Assignee: Michael Musgrove
Fix For: 5.next
TransactionListenerRegistry is for clients to register for transaction related events and
is implemented by the TransactionManager but the SPI does not allow the user to discover
the interface which means they have to write unpleasant code like:
{code}
(TransactionListenerRegistry) getTransactionManager();
{code}
So we need a method in the SPI to get and set an instance of the interface. The setter
will be for the container to set it and the getter is for clients to register interest in
the events
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)