Morbo wrote:

Hello,
This would do the trick :

Code:

public static Date ParseDateFromStringNoThrow(String s) {
try{
return ParseDateFromString(s);
}
catch(ParseException e)
{
//DO SOMETHING USEFULL TO LOG IT
return null;
}
}

Ok, I would like to use something like that, but then, how could I log it using tLogCatcher? I would like to proceed this way because I log errors in a 2nd dataBase and I use all the tLogCatcher outputs to create the database logs. I suspect that using a try/catch/finally block wouldn't allow me to redirect a message to the catcher?

I would design the thing differently... I wouldn't allow garbage in... if you can't parse a field supposed date you should crash the job or log the row in a reject flow....


Anyway, I haven't tried, but what happens when you throw a unchecked exception like derived from RuntimeException ( encapsulate your exception in RuntimeException )? ie.   "throw new RuntimeException(myexception)" ??

You can design your custom parse routine so that it returns value null when the string can't be correctly parsed; then in tmap you can put a filter condition to an additional flow where rows with "null" in the date field go; so you can fully log all the rejected rows ( in file or database ).

bye

Last edited by emaxt6 (2009-08-13 15:16:22)