Originally posted by: venkat10

Hi All,

what is the difference between "xerces and classic" validations while importing type tree using xml schema?

Thanks in advance,

Arjun.

Originally posted by: wtx_genie

Hi Reddy,

 Xerces method will do validation of the input data by definition against the schema. You have to maintain the schema along with project. where as classic does not validate against the schema because entire structure will be imported into the type tree. for example if you have enumeration list for one element in the xsd, then under classic typetree will have restriction list with all enumeration values as specified in the xsd for that element.  But this values you cannot see in the xerces method because when the input data is parsed through the typetree and it gets validated by the xsd file.

Thanks,

WTXgenie

Originally posted by: venkat10

Hi Genie,

Thanks for your reply, and can you give me some more information on this please..

Thanks in advance,

Arjun Reddy.

Originally posted by: paul.brett

Also see this:

http://www-01.ibm.com/support/docview.wss?uid=swg21429791

Thank-you.

Paul.

Follow me on Twitter

Originally posted by: Arun Ramamurthy

Also from my understanding the classic Parser has several limitations in its XML support since its an older method of parsing. As mentioned , the classic parser is a generic parser and can parse any data. It is not dependent on XML rules or the schema once the type tree is created. So it can start in the middle of data as well. Where as the XML parser expects a complete valid XML file to parse. The problem with the classic parser is that there are certain XML rules in the schema that it just can't handle since it uses the older method of parsing , such as "anytype" fields for example.