[jbossts-issues] [JBoss JIRA] (JBTM-969) Specify external participant lifecycle class

[Paul Robinson (Updated) (JIRA)]

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

Paul Robinson updated JBTM-969:
-------------------------------

    Component/s: TXFramework

    
> Specify external participant lifecycle class
> --------------------------------------------
>
>                 Key: JBTM-969
>                 URL: https://issues.jboss.org/browse/JBTM-969
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: TXFramework
>            Reporter: Paul Robinson
>            Assignee: Paul Robinson
>              Labels: TXFramework
>             Fix For: 5.0.0.M2
>
>
> This class level annotation allows the class which is the target of lifecycle handler callbacks to be specified. 
> {code}
> @Retention(RetentionPolicy.RUNTIME)
> @Target(ElementType.TYPE)
> public @interface ParticipantService
> {
>     public Class lifecycleClass() default Default.class;
> }
> {code}
> This field may be overridden in the ServiceRequest annotation itself. If the value of this field is Default.class then the ParticipantService class is used as the default class to resolve POJO lifecycle methods.
> {code}
> @Retention(RetentionPolicy.RUNTIME)
> @Target({ElementType.METHOD, ElementType.TYPE})
> public @interface ServiceRequest
> {
>     public Class lifecycleClass() default Default.class;
> }
> {code}
> If the lifecycleClass attribute is not specified in either place, the class containing the @ServiceInvocation is assumed to also contain the associated Lifecycle Handler methods.

--
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