[jbossts-issues] [JBoss JIRA] Closed: (JBTM-756) deprecate AppServerJDBCXARecovery

Jonathan Halliday (JIRA) jira-events at lists.jboss.org
Thu Jul 22 05:42:39 EDT 2010


     [ https://jira.jboss.org/browse/JBTM-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Halliday closed JBTM-756.
----------------------------------

    Resolution: Done


> deprecate AppServerJDBCXARecovery
> ---------------------------------
>
>                 Key: JBTM-756
>                 URL: https://jira.jboss.org/browse/JBTM-756
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Application Server Integration
>    Affects Versions: 4.11.0, 4.6.1.CP05
>            Reporter: Jonathan Halliday
>            Assignee: Jonathan Halliday
>             Fix For: 4.12.0, 4.6.1.CP06
>
>
> With the addition of recovery auto registration in the JCA for EAP 5.1 and AS 6.M4, AppServerJDBCXARecovery is no longer required. Indeed its continued use in those server versions may cause premature transaction branch rollback in certain circumstances. In order not to break existing user config files the class should continue to be shipped in the next TS release and then removed in the one after. During the transition period it will be disabled by default, with the option to re-enable by appending ",force=true" to the config string.
> see also:
> http://community.jboss.org/thread/92291?start=32&tstart=0
> http://community.jboss.org/wiki/XARecoveryinJCA
> JBAS-8073
> JBPAPP-3638

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbossts-issues mailing list