Post a reply

Write your message and submit

Options

Click in the dark area of the image to send your post.

Go back

Topic review (newest first)

shong
2010-07-21 05:25:44

Hi

-Because the strings are not equal an error is thrown although parsing the date worked.

It is a small bug here, it should ignore case sensitivity and use the method equalsIgnoreCase(object), please report a bug on our bugtracker.

Best regards
Shong

rkuebler
2010-07-20 10:54:48

Hello,

i'm pretty new to TOS but enjoying the power of this tool.
I'm experiencing an Problem, wich occurs when i'm chekcing a Date with the Pattern "dd-MMM-yy".
In and output schema is String. The option "use another schema for compliance check" is used. The type of this schema is date and the pattern is "dd-MMM-yy".
But tSchemaComplianceCheck  component always throws the following error: "the wrong DATE pattern or wrong DATE data".
I debuged the job and found the Problem:
-The MMM in the input string is in capital letters. (07-AUG-08)
-Parsing 07-AUG-08 to date object works
-But the tSchemaComplianceCheck  generates a string of the date object (07-Aug-08) and compares it with the input string (07-AUG-08).
-Because the strings are not equal an error is thrown although parsing the date worked.

The Problem does not occur when the input String is 07-Aug-08 or the "use fastest date check" option of the tSchemaComplianceCheck is used (i dont know the correct english name for this option).

Can someone tell me how to solve this problem without changing the input format, using the "use fastest date check" option or converting the Date manually e.g. with an tMap object.

Thank you for your help

rkuebler

Board footer

Powered by FluxBB