Hi SumitYes that's right, the ids are cached in batches of 10 so the rollback wouldn't have any effect on each delegator.getNextSeqId call.
Regards Scott On 17/07/2009, at 2:17 AM, Sumit Pandit wrote:
Hello Scott, I saw a behavior of system during rollback.In same example if svcA created a primary key with ID = 10000, and if due to any error in svcB then it rollback the transaction.And then in next turn when we try to run it again then it creates the primary key with Id = 10001 (where I was expected for 10000), is this correct?-- Regards Sumit Pandit On Jul 16, 2009, at 6:52 PM, Scott Gray wrote:It depends on what you mean by fail:If svcB triggers a rollback then by default svcA will rollback, see the require-new-transaction attributeIf svcB returns failure then svcA won't roll backIf svcB returns error then svcA will rollback by default, see the break-on-error attributeRegards Scott HotWax Media http://www.hotwaxmedia.com On 17/07/2009, at 12:53 AM, snowch wrote:If have a service (e.g. svcA) that calls another service (e.g. svcB) as perthe pseudo code: svcA: 1. lookup entity 2. modify entity 3. store entity 4. call svcB 5. return If svcB fails, does step 3 rollback? -- View this message in context: http://www.nabble.com/minilang-transactions-tp24515741p24515741.html Sent from the OFBiz - User mailing list archive at Nabble.com.
smime.p7s
Description: S/MIME cryptographic signature
