[
https://issues.jboss.org/browse/JBTM-975?page=com.atlassian.jira.plugin.s...
]
Paul Robinson updated JBTM-975:
-------------------------------
Description:
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. However, a different instance of the class is registered for each @ServiceRequest
method.
By setting the attribute 'single' on @ParticipantService to 'true' allows
the same instance of the LifeCycle class to be used for all @ServiceRequest methods.
{code}
@Retention(RetentionPolicy.RUNTIME)
@Target(ElementType.TYPE)
public @interface ParticipantService
{
public boolean single() default false;
}
{code}
was:
By default if no LifecycleClass is specified on the @ServiceRequest then the same
LifecycleClass is registered for each @ServiceRequest method. However, a different
instance of the class is registered for each @ServiceRequest method.
Allow many ServiceRequest methods to have a single 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: TxBridge
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 5.0.0.M2
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. However, a different instance of the class is registered for each @ServiceRequest
method.
By setting the attribute 'single' on @ParticipantService to 'true' allows
the same instance of the LifeCycle class to be used for all @ServiceRequest methods.
{code}
@Retention(RetentionPolicy.RUNTIME)
@Target(ElementType.TYPE)
public @interface ParticipantService
{
public boolean single() default false;
}
{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