[jbossts-issues] [JBoss JIRA] (JBTM-975) Allow ServiceRequest methods to have own set of lifecycle methods
Paul Robinson (JIRA)
jira-events at lists.jboss.org
Mon Aug 26 07:43:26 EDT 2013
[ https://issues.jboss.org/browse/JBTM-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Robinson resolved JBTM-975.
--------------------------------
Assignee: Paul Robinson
Fix Version/s: 5.0.0.M5
(was: 5.0.0.Final)
Resolution: Out of Date
> Allow ServiceRequest methods to have own set of lifecycle methods
> -----------------------------------------------------------------
>
> Key: JBTM-975
> URL: https://issues.jboss.org/browse/JBTM-975
> 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.M5
>
>
> By default if only one type of LifecycleClass is specified, or if the default of the current class is used, then the same LifecycleClass is registered for each @ServiceRequest method.
> Setting the attribute 'single' on @ParticipantService to 'false' allows a different instance of the LifeCycle class to be used for each @ServiceRequest method.
> {code}
> @Retention(RetentionPolicy.RUNTIME)
> @Target(ElementType.TYPE)
> public @interface ParticipantService
> {
> public boolean single() default true;
> }
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbossts-issues
mailing list