Hi, Le 09/07/2014 18:04, Jon C Kidder a écrit :
I have upgraded my development environment from LSC 2.0.3 to LSC 2.1 and I've noticed a change in error handling that is undesirable in my implementation. In 2.1, one of my tasks encounters a JavaScript error, and then subsequent tasks in the same lsc.xml file don't execute. I'm running the same lsc.xml in my production environment on 2.0.3. It is generating the same errors in the same task, but, subsequent tasks continue to execute. The errors are the result of "garbage" data in the source system. I would like to promote the 2.1 upgrade through all of my environments and into production but for the immediate future can't invest the time in the significant JavaScript updates needed to prevent these "garbage errors". The 2.0.3 behavior is preferred. Is the 2.1 behavior expected or is this a bug?
I don't think this behavior shoud have changed. Can you provide a complete example? Are you sure that is it not due to task reordering (see http://tools.lsc-project.org/issues/589)?
Regards, Raphaël Ouazana. _______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
