IBM Sterling Transformation Extender

Sterling Transformation Extender

Come for answers, stay for best practices. All we're missing is you.


#Sterling
#Supplychain
 View Only
  • 1.  XML validation with XSD specified in Type Tree

    Posted 02/05/08 01:25 PM

    Originally posted by: rarw


    Hi,

    Currently, the XSD must be specified in the XML document in order for parsing to succeed. I would like to eliminate the need to specify the XSD in the XML input file.

    According to the documentation in 1003.pdf (Type Designer), the XSD must be specified in either the Validate As - Location at the DOC level OR in the XML document. That is not true for what I am encountering.

    Any suggestions?

    Thanks,
    Becky
    #DataExchange
    #IBM-Websphere-Transformation-Extender
    #IBMSterlingTransformationExtender


  • 2.  Re: XML validation with XSD specified in Type Tree

    Posted 02/06/08 08:53 AM

    Originally posted by: janhess


    Unles you use the CLASSIC importer, you have to specify the XSD and it has to be available at runtime in the specified location
    #IBMSterlingTransformationExtender
    #DataExchange
    #IBM-Websphere-Transformation-Extender


  • 3.  Re: XML validation with XSD specified in Type Tree

    Posted 02/06/08 03:35 PM

    Originally posted by: rarw


    Thank you janhess – as always, your suggestion worked!

    I re-created the Type Tree using the CLASSIC validation, and then edited the map to work with the new type tree.

    The XML input file is now successfully processed without the XSD being referenced in the file. Also, the XSD was not required in the MAP directory.

    I appreciate your help. Can we send a box of chocolates to your office?

    Thanks,
    Becky
    #DataExchange
    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender