Provide @CompensatedBy annotation --------------------------------- Key: JBTM-1096 URL: https://issues.jboss.org/browse/JBTM-1096 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public(Everyone can see) Components: TXFramework Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.1.Final Original Estimate: 1 week Remaining Estimate: 1 week For example, take this business logic: {code} public class LifecycleImpl { @CompensatedBy(methodName="compensate1") public void doWork1() { //Do work1 } @CompensatedBy(methodName="compensate2") public void doWork2() { //Do work2 } public void compensate1() { //Compensate work1 } public void compensate2() { //Compensate work2 } } {code} Here different compensation methods are specified for the business logic methods 'doWork1' and 'doWork2'. For each call to doWork1, there needs to be a compensation participant registered in that BA, configured with the right compensate method. I think a developer would expect one call of the corresponding compensate, per call to doWorkX. I think the developer would also expect some way of knowing what work they where compensating. For example, having matching parameters and values for the work and compensate methods would allow the compensate to know what it was compensating. This is not going to be trivial to implement as it will probably require some re-factoring to work.

Provide @CompensatedBy annotation --------------------------------- Key: JBTM-1096 URL: https://issues.jboss.org/browse/JBTM-1096 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public(Everyone can see) Components: TXFramework Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.Final Original Estimate: 2 days Remaining Estimate: 2 days For example, take this business logic: {code} public class LifecycleImpl { @CompensatedBy(methodName="compensate1") public void doWork1() { //Do work1 } @CompensatedBy(methodName="compensate2") public void doWork2() { //Do work2 } public void compensate1() { //Compensate work1 } public void compensate2() { //Compensate work2 } } {code} Here different compensation methods are specified for the business logic methods 'doWork1' and 'doWork2'. For each call to doWork1, there needs to be a compensation participant registered in that BA, configured with the right compensate method. I think a developer would expect one call of the corresponding compensate, per call to doWorkX. I think the developer would also expect some way of knowing what work they where compensating. For example, having matching parameters and values for the work and compensate methods would allow the compensate to know what it was compensating. This is not going to be trivial to implement as it will probably require some re-factoring to work.

Provide @CompensatedBy annotation --------------------------------- Key: JBTM-1096 URL: https://issues.jboss.org/browse/JBTM-1096 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public(Everyone can see) Components: TXFramework Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.Final Original Estimate: 2 days Time Spent: 1 day, 4 hours Remaining Estimate: 4 hours For example, take this business logic: {code} public class LifecycleImpl { @CompensatedBy(methodName="compensate1") public void doWork1() { //Do work1 } @CompensatedBy(methodName="compensate2") public void doWork2() { //Do work2 } public void compensate1() { //Compensate work1 } public void compensate2() { //Compensate work2 } } {code} Here different compensation methods are specified for the business logic methods 'doWork1' and 'doWork2'. For each call to doWork1, there needs to be a compensation participant registered in that BA, configured with the right compensate method. I think a developer would expect one call of the corresponding compensate, per call to doWorkX. I think the developer would also expect some way of knowing what work they where compensating. For example, having matching parameters and values for the work and compensate methods would allow the compensate to know what it was compensating. This is not going to be trivial to implement as it will probably require some re-factoring to work.

Provide @CompensatedBy annotation --------------------------------- Key: JBTM-1096 URL: https://issues.jboss.org/browse/JBTM-1096 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public(Everyone can see) Components: TXFramework Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.1.Final Original Estimate: 2 days Time Spent: 1 day, 4 hours Remaining Estimate: 4 hours For example, take this business logic: {code} public class LifecycleImpl { @CompensatedBy(methodName="compensate1") public void doWork1() { //Do work1 } @CompensatedBy(methodName="compensate2") public void doWork2() { //Do work2 } public void compensate1() { //Compensate work1 } public void compensate2() { //Compensate work2 } } {code} Here different compensation methods are specified for the business logic methods 'doWork1' and 'doWork2'. For each call to doWork1, there needs to be a compensation participant registered in that BA, configured with the right compensate method. I think a developer would expect one call of the corresponding compensate, per call to doWorkX. I think the developer would also expect some way of knowing what work they where compensating. For example, having matching parameters and values for the work and compensate methods would allow the compensate to know what it was compensating. This is not going to be trivial to implement as it will probably require some re-factoring to work.