Originally posted by: SystemAdmin
Can't you also validate against the XSD by specifying it in the Doc properties? It appears that the standard validation takes place followed by the XSD validation by the external parser. Here's an example of what followed the standard (and successful) validation trace:
External Parser returned Error:
TYPE X
'0003' (Error
line: 23 column: 47
Datatype error: Type:InvalidDatatypeValueException, Message:Value
'040-404-0404' does not match regular expression facet
'(\+
^\-+{1,25}-)?(
^\-+{1,25}-)?(
^\-+{1,25})(\+
^\-+{1,25})?'.
Error
line: 53 column: 48
Datatype error: Type:InvalidDatatypeValueException, Message:Value
'913-422-9303' does not match regular expression facet
'(\+
^\-+{1,25}-)?(
^\-+{1,25}-)?(
^\-+{1,25})(\+
^\-+{1,25})?'.
Error
line: 70 column: 47
Datatype error: Type:InvalidDatatypeValueExcep).
(Level 0: Offset 0, len 2921, comp 1 of 0, #1, DI 000000A9:)
Data at offset 0 (
'<?xml version="1') was found to be of TYPE
X
'0002' (DocGroup XSD).
INPUT 1 was valid, but it contained invalid objects.
#IBM-Websphere-Transformation-Extender#DataExchange#IBMSterlingTransformationExtender