[JBoss JIRA] (JBTM-977) Specify the order in which lifecycle methods are invoked when multiple of the same type exist
2:27 p.m.
Specify the order in which lifecycle methods are invoked when multiple of the same type
exist
---------------------------------------------------------------------------------------------
Key: JBTM-977
URL: https://issues.jboss.org/browse/JBTM-977
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
A LifecycleClass implementation should be able to register multiple methods with the same
Lifecycele annotation. For example, this would allow more than one compensation method to
be triggered.
Example:
{code}
@ServiceRequest()
public void submitOrder(...)
{
...
}
@Compensate
public void cancelOrder()
{
//Cancel the order
}
@Compensate
public void notifyAdmin()
{
//Notify an admin that an order was cancelled.
}
{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
2:31 p.m.
[
https://issues.jboss.org/browse/JBTM-977?page=com.atlassian.jira.plugin.s...
]
Paul Robinson updated JBTM-977:
-------------------------------
Description:
The 'order' attribute on Lifecycle callback annotations (e.g. @Compensate,
@Prepare) can be used to ensure that certain lifecycle callbacks precede others during
lifecycle processing. Normally, callbacks are made in the reverse order to that in which
their corresponding service request was made. FIRST indicates that the callback should be
executed before other NORMAL callbacks registered for the same lifecycle event. LAST
indicates that the callback should be executed after other NORMAL callbacks registered for
the same lifecycle event. Multiple FIRST or LAST callbacks are sorted in reverse order of
registration.
Example:
{code}
@ServiceRequest()
public void submitOrder(...)
{
...
}
@Compensate
public void cancelOrder()
{
//Cancel the order
}
@Compensate(order=ExecutionOrder.LAST)
public void notifyAdmin()
{
//Notify an admin that an order was cancelled.
}
{code}
was:
A LifecycleClass implementation should be able to register multiple methods with the same
Lifecycele annotation. For example, this would allow more than one compensation method to
be triggered.
Example:
{code}
@ServiceRequest()
public void submitOrder(...)
{
...
}
@Compensate
public void cancelOrder()
{
//Cancel the order
}
@Compensate
public void notifyAdmin()
{
//Notify an admin that an order was cancelled.
}
{code}
Specify the order in which lifecycle methods are invoked when
multiple of the same type exist
---------------------------------------------------------------------------------------------
Key: JBTM-977
URL: https://issues.jboss.org/browse/JBTM-977
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
The 'order' attribute on Lifecycle callback annotations (e.g. @Compensate,
@Prepare) can be used to ensure that certain lifecycle callbacks precede others during
lifecycle processing. Normally, callbacks are made in the reverse order to that in which
their corresponding service request was made. FIRST indicates that the callback should be
executed before other NORMAL callbacks registered for the same lifecycle event. LAST
indicates that the callback should be executed after other NORMAL callbacks registered for
the same lifecycle event. Multiple FIRST or LAST callbacks are sorted in reverse order of
registration.
Example:
{code}
@ServiceRequest()
public void submitOrder(...)
{
...
}
@Compensate
public void cancelOrder()
{
//Cancel the order
}
@Compensate(order=ExecutionOrder.LAST)
public void notifyAdmin()
{
//Notify an admin that an order was cancelled.
}
{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
2:35 p.m.
[
https://issues.jboss.org/browse/JBTM-977?page=com.atlassian.jira.plugin.s...
]
Paul Robinson updated JBTM-977:
-------------------------------
Labels: TXFramework (was: )
Component/s: (was: TxBridge)
Specify the order in which lifecycle methods are invoked when
multiple of the same type exist
---------------------------------------------------------------------------------------------
Key: JBTM-977
URL: https://issues.jboss.org/browse/JBTM-977
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
The 'order' attribute on Lifecycle callback annotations (e.g. @Compensate,
@Prepare) can be used to ensure that certain lifecycle callbacks precede others during
lifecycle processing. Normally, callbacks are made in the reverse order to that in which
their corresponding service request was made. FIRST indicates that the callback should be
executed before other NORMAL callbacks registered for the same lifecycle event. LAST
indicates that the callback should be executed after other NORMAL callbacks registered for
the same lifecycle event. Multiple FIRST or LAST callbacks are sorted in reverse order of
registration.
Example:
{code}
@ServiceRequest()
public void submitOrder(...)
{
...
}
@Compensate
public void cancelOrder()
{
//Cancel the order
}
@Compensate(order=ExecutionOrder.LAST)
public void notifyAdmin()
{
//Notify an admin that an order was cancelled.
}
{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
12:05 p.m.
[
https://issues.jboss.org/browse/JBTM-977?page=com.atlassian.jira.plugin.s...
]
Paul Robinson updated JBTM-977:
-------------------------------
Component/s: TXFramework
Specify the order in which lifecycle methods are invoked when
multiple of the same type exist
---------------------------------------------------------------------------------------------
Key: JBTM-977
URL: https://issues.jboss.org/browse/JBTM-977
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
The 'order' attribute on Lifecycle callback annotations (e.g. @Compensate,
@Prepare) can be used to ensure that certain lifecycle callbacks precede others during
lifecycle processing. Normally, callbacks are made in the reverse order to that in which
their corresponding service request was made. FIRST indicates that the callback should be
executed before other NORMAL callbacks registered for the same lifecycle event. LAST
indicates that the callback should be executed after other NORMAL callbacks registered for
the same lifecycle event. Multiple FIRST or LAST callbacks are sorted in reverse order of
registration.
Example:
{code}
@ServiceRequest()
public void submitOrder(...)
{
...
}
@Compensate
public void cancelOrder()
{
//Cancel the order
}
@Compensate(order=ExecutionOrder.LAST)
public void notifyAdmin()
{
//Notify an admin that an order was cancelled.
}
{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
2:07 p.m.
[
https://issues.jboss.org/browse/JBTM-977?page=com.atlassian.jira.plugin.s...
]
Paul Robinson updated JBTM-977:
-------------------------------
Fix Version/s: 5.0.0.Final
(was: 5.0.0.M2)
Specify the order in which lifecycle methods are invoked when
multiple of the same type exist
---------------------------------------------------------------------------------------------
Key: JBTM-977
URL: https://issues.jboss.org/browse/JBTM-977
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.Final
The 'order' attribute on Lifecycle callback annotations (e.g. @Compensate,
@Prepare) can be used to ensure that certain lifecycle callbacks precede others during
lifecycle processing. Normally, callbacks are made in the reverse order to that in which
their corresponding service request was made. FIRST indicates that the callback should be
executed before other NORMAL callbacks registered for the same lifecycle event. LAST
indicates that the callback should be executed after other NORMAL callbacks registered for
the same lifecycle event. Multiple FIRST or LAST callbacks are sorted in reverse order of
registration.
Example:
{code}
@ServiceRequest()
public void submitOrder(...)
{
...
}
@Compensate
public void cancelOrder()
{
//Cancel the order
}
@Compensate(order=ExecutionOrder.LAST)
public void notifyAdmin()
{
//Notify an admin that an order was cancelled.
}
{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
4530
days inactive
4532
days old
jbossts-issues@lists.jboss.org
4 comments
2 participants
participants (2)
-
Paul Robinson (Created) (JIRA) -
Paul Robinson (Updated) (JIRA)