XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Show tree view Topic
Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Go to previous topicPrev TopicGo to next topicNext Topic
Postnext
Nitesh JaruharSubject: handling abstract types in the mapper (XSLT)
Author: Nitesh Jaruhar
Date: 21 Dec 2006 03:31 AM
Hi,

In the source XSD one of the elements is declared to have the abstract type - we want to map this to various target XSD elements

Currently there are two options:
(1) manually write XSLT to handle the mapping depending on the xsi:type in the source XML
(2) (preferred) use SS to map the element and its subsequent elements (which are dependent on the xsi:type)

Is there anyway to do (2)? If so, appreciate if someone can point me to a manual/how-to. Even if it means we have to temproraly edit the source XSD to allow us to use the mapper (currently SS does not realise that the source element is based on an abstract type and after mapping it simply does a value-of of that one source element)

i.e.
if type = Gas then map
sourceelementA to targetelement A
sourceelementB to targetelement B
sourceelementC to targetelement C
else if type = Electicity
sourceelementD to targetelement A
sourceelementE to targetelement B
sourceelementF to targetelement G

where all the "sourceelement?" are part of the abstract type definition.

Thanks,
Nitesh

Postnext
Minollo I.Subject: handling abstract types in the mapper (XSLT)
Author: Minollo I.
Date: 21 Dec 2006 09:23 AM
Any chance you can share with us the source/target schemas so that we can show you how to do that in more concrete terms?

Postnext
Nitesh JaruharSubject: handling abstract types in the mapper (XSLT)
Author: Nitesh Jaruhar
Date: 21 Dec 2006 05:17 PM
Hi,

Below is a snipet of the XSD using the abstract type. Attached is the abstract type definition (oexml_MeterRead_r1.txt). Also, attached is the target XSD. So for example, if its 'Gas..' type then we need to map the GasMeterReadStatus in the source to 'ReadStatus' in the target; while if its 'Electricity' then we map ElectricityMeterReadStatus to 'ReadStatus'.

<xsd:complexType name="MeterReadingHistoryResponse">
<xsd:annotation>
<xsd:documentation>
Purpose -
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="BaseResponseR1">
<xsd:sequence>
<xsd:element name="NMI" type="NMI" minOccurs="0"/>
<xsd:element name="PropertyID" type="PropertyID" minOccurs="0"/>
<xsd:element name="MeterReadingData" type="MeterReadData" minOccurs="0"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>

Please let me know if I can use the SS GUI to do this or if I need to manually code it via choose-when-otherwise (bit of a hassle considerring we have > 200 of these).

Thanks,
Nitesh


Documentoexml_MeterRead_r1.txt
MeterReading abstract type declaration

UnknownINT350_Response_edited.xsd
target xsd

Postnext
Nitesh JaruharSubject: handling abstract types in the mapper (XSLT)
Author: Nitesh Jaruhar
Date: 07 Jan 2007 10:58 PM
any updates to this

Posttop
Minollo I.Subject: handling abstract types in the mapper (XSLT)
Author: Minollo I.
Date: 07 Jan 2007 11:36 PM
The schema you attached (oexml_MeterRead_r1) misses some type definitions; we could more easily show you an example if we had a sample XML input.

Anyway, what you are looking for should be possible creating a choose block in mapper, creating conditions for the specific type instances you find in the XML input (like "name() = 'Gas...'"), and for each condtion creating the proper mappings.

As I mentioned, a sample XML input might make it easier to show an example.

 
Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Go to previous topicPrev TopicGo to next topicNext Topic
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!  
go

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.