[
http://jira.jboss.com/jira/browse/JBTM-319?page=comments#action_12394694 ]
Jonathan Halliday commented on JBTM-319:
----------------------------------------
The existing JNDIXARecovery approach is almost right, except it reads datasource
parameters from a xml file. For integration with AS, it would be better if we have a
similar module that just takes a JNDI name for the DataSource and looks it up from the
AS.
Requiring manual configuration of this is not elegant, since new xa data source then need
defining in the -ds.xml for the AS and their JNDI name referencing the in
jbossjta-properties.xml for TS recovery.
It would be possible to walk the JNDI tree at startup and populate the recovery system
with one instance of this Recovery class per defined XADataSource, but it's
problematic for two reasons: data sources may not yet be deployed at that time and we may
not want to recovery for them e.g. if they are shared with other systems.
Ideally the AS code that does deployment of XADataSources should call the recovery system
when it does so, perhaps conditional on a flag in the -ds.xml so that recovery could be
disabled on a per-datasource basis in the config ds file.
Until then the config will have to remain split between the -ds.xml and the ts properties
file.
Update JNDI recovery to cope with WrappedDataSource
---------------------------------------------------
Key: JBTM-319
URL:
http://jira.jboss.com/jira/browse/JBTM-319
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public(Everyone can see)
Components: JTA Implementation, Recovery
Affects Versions: 4.2.3.SP6
Reporter: Mark Little
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira