Originally posted by: SystemAdmin

when we import the schema as Xerces, Does the XML being supplied for the map should also have Schema definition like this.Because when I use classic it does not require the schema definition. We can simply start and end the tags in the order.

<recordAgreement xmlns="XYZ" xmlns:xsi="XYZ" xsi:schemaLocation="XYZ">

----
----
</recordAgreement>

Thank you
--Abhilash

Message was edited by: MasterMind
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

when you select xerces to import a tree, you need xsd file to run the map.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: gnanasiva

You need not have any thing special to the schema...

The real difference in opting for xerces and classic are some of the properties will be displayed exclusivley in the type tree whn u choose xerces, though those details will be incorped with classic, it will not be dispalyed...

Siva
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: vickey

There are couple of advantages of Xceres.

1) You will not be able to change the properties of the groups or Items.
2) If any invalid or control character comes in the input then the map throws the error "One or more Inputs Invalid". This validation dosent happen in 6.7
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: SystemAdmin

Thank you Guys
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange