Hello,
I would require a new behavior for 4.2.2 version.
I am using Spring to manager transactions in my batch processing. I need do fine-tuning transactions by programmatic transaction (http://docs.spring.io/spring-framework/docs/current/spring-framework-reference/html/transaction.html#transaction-programmatic-ptm)
To nested transactions, I need that PipelineListener methods (beforeRecordProcessing, afterRecordProcessing) be called in a certain order. If the pipelines a, b and c are registered in this order, then the beforeRecordProcessing methods should be called in same order (a.beforeRecordProcessing, b.beforeRecordProcessing, c.beforeRecordProcessing), and the afterRecordProcessing should be called in inverse order (c.afterRecordProcessing, b.afterRecordProcessing, a.afterRecordProcessing).
a.beforeRecordProcessing
b.beforeRecordProcessing
c.beforeRecordProcessing
(pipeline processing)
c.afterRecordProcessing
b.afterRecordProcessing
a.afterRecordProcessing
Thanks
Hello,
I would require a new behavior for 4.2.2 version.
I am using Spring to manager transactions in my batch processing. I need do fine-tuning transactions by programmatic transaction (http://docs.spring.io/spring-framework/docs/current/spring-framework-reference/html/transaction.html#transaction-programmatic-ptm)
To nested transactions, I need that PipelineListener methods (beforeRecordProcessing, afterRecordProcessing) be called in a certain order. If the pipelines a, b and c are registered in this order, then the beforeRecordProcessing methods should be called in same order (a.beforeRecordProcessing, b.beforeRecordProcessing, c.beforeRecordProcessing), and the afterRecordProcessing should be called in inverse order (c.afterRecordProcessing, b.afterRecordProcessing, a.afterRecordProcessing).
a.beforeRecordProcessing
b.beforeRecordProcessing
c.beforeRecordProcessing
(pipeline processing)
c.afterRecordProcessing
b.afterRecordProcessing
a.afterRecordProcessing
Thanks