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 Go to previous topicPrev TopicGo to next topicNext Topic
Postnext
Wim DecorteSubject: XSLT - mapper: changes source of target XML file
Author: Wim Decorte
Date: 01 Mar 2004 06:49 AM
Hi all,

I need to transform one XML file to another one (and vice versa). The target XML has a bunch of nodes under a node. Each node is the name of a db field. The idea is to put values from the source XML into those fields in the target.

However, when I open the target XML in the mapper window, I can only see one node. Sure I can create the other ones and map properly but it's a drag. Is there any way of telling Stylus to not interpret the target XML and just leave it alone?

Postnext
(Deleted User) Subject: RE: XSLT - mapper: changes source of target XML file
Author: (Deleted User)
Date: 01 Mar 2004 07:32 AM
hi Wim,

the way to do it in stylus is 'Duplicate Node'. you can do it through right
click on the FIELD node and invoke 'Duplicate Node' from the context menu.
Repeating same step will result in multiple 'FIELD' nodes.

hope this helps.

song.


> -----Original Message-----
> From: stylus-studio-xslt Listmanager [mailto:listmanager@edn.exln.com]
> Sent: Monday, March 01, 2004 7:16 AM
> To: Recipients of 'stylus-studio-xslt' suppressed
> Subject: XSLT - mapper: changes source of target XML file
>
>
> From: "Wim Decorte"
>
> Hi all,
>
> I need to transform one XML file to another one (and vice versa).
> The target XML has a bunch of nodes under a
> node. Each node is the name of a db
> field. The idea is to put values from the source XML into those
> fields in the target.
>
> However, when I open the target XML in the mapper window, I can
> only see one node. Sure I can create the other ones and
> map properly but it's a drag. Is there any way of telling Stylus
> to not interpret the target XML and just leave it alone?
>
>
>
> To reply: mailto:stylus-studio-xslt.7219@edn.exln.com
> To start a new topic: mailto:stylus-studio-xslt@edn.exln.com
> To login: http://edn.exln.com/~SSDN
>

Postnext
Wim DecorteSubject: RE: XSLT - mapper: changes source of target XML fi
Author: Wim Decorte
Date: 01 Mar 2004 08:05 AM
Thanks, Song.

That's what I figured. But since there are over 50 field nodes, it's a bit of an annoyance.

Wim

Postnext
(Deleted User) Subject: RE: XSLT - mapper: changes source of target XML fi
Author: (Deleted User)
Date: 01 Mar 2004 08:24 AM
hi, Wim

if all the 50 fiedls are transformed in a simmilar way, I'm not sure
manullay mapping one to one from source to target is your best choice. you
may better off thinking about your transformation logic and come up with a
generic stylesheet to do your tranformation.


song.

> -----Original Message-----
> From: stylus-studio-xslt Listmanager [mailto:listmanager@edn.exln.com]
> Sent: Monday, March 01, 2004 8:33 AM
> To: Recipients of 'stylus-studio-xslt' suppressed
> Subject: RE: XSLT - mapper: changes source of target XML fi
>
>
> From: "Wim Decorte"
>
> Thanks, Song.
>
> That's what I figured. But since there are over 50 field nodes,
> it's a bit of an annoyance.
>
> Wim
>
>
>
> To reply: mailto:stylus-studio-xslt.7223@edn.exln.com
> To start a new topic: mailto:stylus-studio-xslt@edn.exln.com
> To login: http://edn.exln.com/~SSDN
>

Postnext
Wim DecorteSubject: RE: XSLT - mapper: changes source of target XML fi
Author: Wim Decorte
Date: 01 Mar 2004 09:25 AM
Thanks for following up, Song.

Each source node has to be mapped to the correct field node in the target XML, which is why I would need the 50 or so field nodes in the target XML to show.

It's basically a 1 record to 1 record field remapping to prepare an XML in the grammar that is supported for import in the database.

Wim.

Posttop
Greg RatajikSubject: RE: XSLT - mapper: changes source of target XML fi
Author: Greg Ratajik
Date: 10 Oct 2005 04:29 PM
We've got the same issue. We have to map into a XML that's basically a DB's structure (no choice here, it's for a export to another system).

<RECORDS>
<RECORD>
<TableName>Table1</TableName>
<FIELDS>
<Field1></Field1>
<Field2></Field2>
</FIELDS>
</RECORD>
<RECORD>
<TableName>Table2</TableName>
<FIELDS>
<Field3></Field3>
<Field4></Field4>
</FIELDS>
</RECORD>
<RECORD>
<TableName>Table3</TableName>
<FIELDS>
<Field5></Field5>
<Field6></Field6>
</FIELDS>
</RECORD>
</RECORDS>


When we bring this in as the target for the mapper, it ends up showing this:

<RECORDS>
<RECORD>
<TableName></TableName>
<FIELDS>
<Field1></Field1>
<Field2></Field2>
<Field3></Field3>
<Field4></Field4>
<Field5></Field5>
<Field6></Field6>
</FIELDS>
</RECORD>
</RECORDS>


So each duplicate node name ends up being merged in. We create the target by hand, but it's a massive XML document so it will end up taking a large amount of time to do - if there's some way to get Stylus to correctly read the structure, it will save us a lot of time...

Thanks,
-Greg

 
Topic Page 1 2 3 4 5 6 7 8 9 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.