[jbossts-issues] [JBoss JIRA] (JBTM-984) Support @Recover and @RecoverComplete annotations in the TXFramework

Paul Robinson (Updated) (JIRA) jira-events at lists.jboss.org
Mon Nov 28 11:52:41 EST 2011


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

Paul Robinson updated JBTM-984:
-------------------------------

    Description: 
LifecycleHandler classes can use the METHOD annotations @Recover and @RecoverComplete to perform recovery. @Recover's method should be called for each recovered object before allowing lifecycle processing to proceed for participants recovered from the log. The second method should be called once all recovered participants have completed, allowing the LifecycleHandler class to clear up records for transactions which were not resolved by recovery processing.
The target method for an @Recover annotation should have void type and take a single argument which should be type-compatible with the type of any saved object.
The target method for an @RecoverComplete annotation should have void type and take no arguments.

The recovery mechanism which needs to reload saved objects and presents them back to the service class during recovery processing as a precursor to actually running lifecycle callbacks for recovered transactions. This is done through the Control interface:

{code}
public interface TxControl
{
    public String storeObject(Serializable object);
    public boolean deleteObject(String identifier);
}
{code}


  was:A simple test should be able to check this.


    
> Support @Recover and @RecoverComplete annotations in the TXFramework
> --------------------------------------------------------------------
>
>                 Key: JBTM-984
>                 URL: https://issues.jboss.org/browse/JBTM-984
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Paul Robinson
>            Assignee: Paul Robinson
>              Labels: TXFramework
>             Fix For: 5.0.0.M2
>
>
> LifecycleHandler classes can use the METHOD annotations @Recover and @RecoverComplete to perform recovery. @Recover's method should be called for each recovered object before allowing lifecycle processing to proceed for participants recovered from the log. The second method should be called once all recovered participants have completed, allowing the LifecycleHandler class to clear up records for transactions which were not resolved by recovery processing.
> The target method for an @Recover annotation should have void type and take a single argument which should be type-compatible with the type of any saved object.
> The target method for an @RecoverComplete annotation should have void type and take no arguments.
> The recovery mechanism which needs to reload saved objects and presents them back to the service class during recovery processing as a precursor to actually running lifecycle callbacks for recovered transactions. This is done through the Control interface:
> {code}
> public interface TxControl
> {
>     public String storeObject(Serializable object);
>     public boolean deleteObject(String identifier);
> }
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbossts-issues mailing list