IBM Sterling Transformation Extender

Originally posted by: SystemAdmin

Hello Guys,
I am working on XML schemas (XSD's).
My problem is when I import a XSD (Using Classic) and create a type tree and later use this type tree in the MAP.

It all says "one or more inputs are invalid". I tried to validate the XML(Input file) with the schema every thing looks fine.

But when I change the XML input in this format it works fine.

<tag1>
<tag2>
<tag3>
</tag3>
</tag2>
</tag1>

TO

<tag1><tag2><tag3></tag3></tag2 ></tag1>

Problem here is Input XML for this Map is coming with First format and I need a find a solution for this.

Please let me know If any one has faced this problem and solved. by the way I am using 8.0 edition

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

Originally posted by: TarunB

Are you saying that the XML file is provided with <CR><LF> (or just <LF> if on Unix) after each tag?

The XML type tree should allow for this. If you are having problems determining this, then you can work around it by creating a pre-processing map to read in the XML data (with line feeds) as a blob record, and SUBSTITUTE all of the <CR><LF> with nothing.

Then you can drop off the amended file for processing by the real map.
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

Thanks for the reply.Yes, I tried this one the problem persisted even though I remove <CR><LF> from XML its not reading all the elements only when I remove all the spaces with <CR><LF> between tags its working. I found a function in 8.2 called as NORMXML() this is what I need to implement in 8.0. which I need to find out. Is there any better way to read XML trace?
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: janhess

White space between your tags shouldn't be a problem if the type tree is defined correctly.
I think your version 8.0 probably has bugs in the XML processing. This seems to happen a lot with new releases. Ensure you have the latest patches from IBM
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

"if the type tree is defined correctly" What exactly do you mean by that? I just imported Schema and making use of that do we need to change in the TypeTree after importing. I am using 8.0(105) bulid I will check on the Updates. Thank you
--Abhilash
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: janhess

If there are bugs it may not define the type tree correctly.
Can you attach the xsd and sample xml. I can try importing into different versions.
Have you got service pack 1 applied? I can't remember what build that produces.
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

I have attached a sample XML & schema I guess all the tags are optional.
Thank you
--Abhilash
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: janhess

Well it works at 8.1 if imported with Xerces but doesn't seem to work at any version using Classic. Must be a bug or a feature of the XSD that isn't supported in Classic mode.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: SystemAdmin

it works well when I use 8.2 as you said. In 8.0 there was some errors with Xerces importer saying "This GROUP must have at least one component" So, when I added some Optional Elements in the complex type of the schema it went through well. Thank you Guys
--Abhilash
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender