Originally posted by: DennisRitche
Hi paul,
Thanks for the response ....!
I think the "well formed" option will ignore the restrictions/size validations that has been defined in XSD , right?
Here i am talking about a case where there may be a possibility of receiving elements in xml which are not defined in xsd/typetree , does Well formed option valid in this case?
Defining my case with an example:
**************************************************************
XSD:
<xs:schema
attributeFormDefault
=
"unqualified"
elementFormDefault
=
"qualified"
xmlns:xs
=
"http://www.w3.org/2001/XMLSchema"
>
<xs:element
name
=
"note"
>
<xs:complexType>
<xs:sequence>
<xs:element
type
=
"xs:string"
name
=
"
to"
/>
<xs:element
type
=
"xs:string"
name
=
"
from"
/>
<
/xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
here only the two elements "to" and "from" are defined
********************************************************************************************
XML:
<note>
<to>Tove</to>
<from>Jani</from>
<heading>Reminder</heading>
<body>Don't forget me this weekend!</body>
</note>
here in xml two undefined elements have been received and the map should not throw error for this case since those will not be passed to downstream(i mean no mapping for these two elements)
********************************************************************
Coming to the second option using XPATH:
here in this case i am successful for some extent , but i am unable to handle the multiple occurrences situation , i mean a group(1:s) need to be mapped since the group occurrences is undefined , i cannot go with indexing , could we do in some other way?
#IBM-Websphere-Transformation-Extender#DataExchange#IBMSterlingTransformationExtender