XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
search
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Home » Boards » Stylus Studio Developer Network » XSLT Help and Discussion » XSLT - mapper: changes source of target XML file
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
+ Stylus Studio Technical Forum (14621)
+ Website Feedback (249)
- XSLT Help and Discussion (7625)
-> + how to insert un return in the... (2)
-> + String in a range (5)
-> + To identify the right edition (4)
-> + Flow Control Feature (2)
-> + calling nested external functi... (3)
-> + Replacing commas with a blank (6)
-> + Grouping very urgent . (2)
-> + xsl node number (3)
-> + Wordml intelligence (6)
-> + Preview and backmapping for wo... (5)
-> + XSLT - find line numbers of di... (2)
-> + The last five bytes of a varia... (7)
-> + simple problem but i'm a bit t... (3)
-> + H plz help me (2)
-> + XSLT : Very Urgent Requirement (7)
-> + comparing two xml files (3)
-> + Support for xsl created from w... (4)
-> + Wildcard Param (3)
-> + XSLT OutOfMemoryError (3)
-> + How can I output the filename ... (7)
-> + How do I strip out a comma ast... (8)
-> + xslt current-dateTime() not re... (2)
-> + Exceed the maximum recursion d... (8)
-> + Saxon9 "java.net.ConnectExcept... (2)
-> - Help Required (1)
-> + XSLT Help to get value from Up... (2)
-> + Date Functions (5)
-> + Need to unescape < and > (2)
-> + No Topic (2)
-> + Problem with handling multiple... (3)
-> + Question XPath expression (dis... (2)
-> + New user, basic question (2)
-> + Serializing XML to a string wi... (2)
-> + Node already has a control li... (2)
-> + Trying to access the position ... (5)
-> + XSLT Help (2)
-> + XSLT, Microsoft Access, and re... (4)
-> + saxon:assign usage problem. (5)
-> + Help with XSLT mapping require... (4)
-> + Muenchian Grouping problem (6)
-> + Automatic postprocessing (2)
-> + Problem Setting Variable (3)
-> - Problem Setting Variable (1)
-> + Looping question (14)
-> + Attribute Centeric XML from Re... (2)
-> + How do I do this ? (2)
-> + Accessing an attribute based o... (3)
-> + help needed - using saxon thro... (2)
-> + Grouping Problem still (6)
-> + Use XSL-FO to create tables fr... (6)
-> + taking out a child and (6)
-> + Yet another problem (3)
-> + using XSL-FO to convert PDF (4)
-> + Preventing namespace declarati... (2)
-> + Small problem during conversio... (4)
-> + Problems removing namespaces (2)
-> + Grouping/Following question (4)
-> + Transforming XML into another ... (3)
-> + Help Needes (3)
-> - Help needed! (1)
-> + Conv of DSML Format to XML for... (2)
-> - Regd, entering text in the t... (1)
-> + displaying all the text around... (4)
-> + inserting values into empty ta... (5)
-> + How to get rid of xmlns="" att... (3)
-> + XSLT How to include the '<' sy... (2)
-> - HELP: Functional XSLT Implemen... (1)
-> - Cannot find a matching 1-argum... (1)
-> + XSLT a:? (2)
-> + Attribute Value Concatenation (2)
-> - Why is the WYSIWYG xslt editor... (1)
-> + WebService Call Error: Ref ele... (4)
-> + How to replace value of a fiel... (2)
-> + Schema Validation Problems (3)
-> + Reusing a prior valid value in... (5)
-> + Clutching at straws! (2)
-> + Adding a number to a for each ... (2)
-> + Transform Name Value pairs int... (4)
-> + Transform the XML Scheme with ... (2)
-> + create XML drop down lists (2)
-> + error during stylesheet tutori... (3)
-> + Modify the value in a element ... (2)
-> + Call to extension function fai... (2)
-> + Convert XML Schema to XML - Mi... (2)
-> + How to calculate maximun RowCo... (3)
-> + Help with using not(preceding:... (5)
-> - Please Help me on this XML to ... (1)
-> + Paasing Parameter Values From ... (6)
-> + XSLT Transformation w/ namespa... (3)
-> + For-each select and parameter ... (3)
-> + Using < (less than) operator (5)
-> + Inserting carriage return (spe... (3)
-> + Inserting carriage return (spe... (2)
-> + Help with SerializerTrace erro... (8)
-> + xml to x3d (5)
-> + Exiting processing loop early (2)
-> + Easy way to Convert One source... (3)
-> + XSLT Editor tab missing from D... (2)
-> + Writing strings of characters ... (4)
-> + Adding the content of an eleme... (3)
-- Previous [601-620] [621-640] [641-660] Next
+ XQuery Help and Discussion (2017)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (364)
+ Stylus Studio Announcements (113)
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
   
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.