Thanks for the clarification David. I have been using require-new-transaction when calling services, but as far as I can tell there is not an equivalent option for calling simple methods. For example, I am calling the simple-method "createPersonRoleAndContactMechs" which is not defined as a service. If I wanted to use a transaction for each iteration I would need to create a service definition for the simple method, correct?
Vince Clark [email protected] (303) 493-6723 ----- Original Message ----- From: "David E Jones" <[email protected]> To: [email protected] Sent: Wednesday, July 22, 2009 3:53:08 PM GMT -07:00 US/Canada Mountain Subject: Re: error handling in simple methods To clarify: the sub-method (sub-service really) would ONLY be in a separate transaction if you use the require-new-transaction attribute on the service definition. -David On Jul 22, 2009, at 3:48 PM, BJ Freeman wrote: > another approach may be to call another simple method from the > iterate. > that method does the store and you can use use-transaction > this would make it per record. > > Vince Clark sent the following on 7/22/2009 2:02 PM: >> I am importing a large amount of customer and order data. I am >> iterating thru the result set using the simple-method <iterate> tag >> and if I hit one bad record the whole job fails. How can I trap and >> log errors and continue? >> >> >> Vince Clark >> [email protected] >> (303) 493-6723 >> > > -- > BJ Freeman > http://www.businessesnetwork.com/automation > http://bjfreeman.elance.com > http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro > Systems Integrator. >
