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 » XML Mapper Limitations
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
+ Stylus Studio Technical Forum (14621)
+ Website Feedback (249)
- XSLT Help and Discussion (7625)
-> + Remove leading Zeros from a st... (4)
-> + how to parse a html element fo... (2)
-> + Add namespaces to target messa... (2)
-> + XSLT Transformation - insertin... (3)
-> + Convert binary xml (9)
-> + XSLT Transformation (4)
-> + Generating hyperlinks (3)
-> + XSLT to PDF problem (with JAVA... (2)
-> + how to add onclick_ with try/c... (2)
-> + Keep table in one page. xsl-fo... (4)
-> + Cannot find a matching 2-argum... (3)
-> + Creating one string from a sub... (2)
-> + XSLT: Traversing XML twice for... (6)
-> + Copy element without namespace... (5)
-> + Create dynamic elemant name (2)
-> + XSLT: Traversing XML twice for... (3)
-> + Problem including Javascript (2)
-> + Looping through attributes (4)
-> + Transform values into elements... (4)
-> + Problem with deep node copy an... (2)
-> + Comparing Dates With ASP.NET 2... (3)
-> + Converting tree structure to h... (4)
-> + Attributes to element transfor... (2)
-> + XSLT transformation (2)
-> + XSLT transformation (5)
-> + xsl:character-map not working (2)
-> + Removing duplicates entries. (2)
-> + Image issues. (2)
-> + xsl transformation (4)
-> + XSL Question (5)
-> + how to insert xml file as an n... (2)
-> + Document Function (2)
-> + convert seconds to hh:mm:ss (5)
-> + how to remove attribute while ... (3)
-> + XSL-FO question (2)
-> + EDI 997 creation. (7)
-> + Line break within a tag in XML... (2)
-> + Contact Help Needed (2)
-> + ACK 997 (2)
-> + XSLT to output XML( which conf... (11)
-> + Retrieving all nodes where a c... (6)
-> + Verifying XML and XSD within X... (4)
-> + How to validate date format in... (3)
-> + XSLT question (2)
-> + Muenchian grouping (2)
-> + How to remove specific text en... (8)
-> + If Else Condition along with L... (2)
-> + SAXON Problem (2)
-> + comapring global variable valu... (2)
-> + copying the value of xsl in va... (2)
-> + Urgent:XSLT element value sel... (2)
-> + Ignoring first element using f... (2)
-> + EDI X12 to XML (4)
-> + XSLT FOR-EACH HELP (2)
-> + Sorting Help Needed (3)
-> + XSLT help with linking (2)
-> + selecting data into node set b... (2)
-> + Watch and Variable in Debug no... (4)
-> + Transforming XML to XML - grou... (2)
-> + Saxon 9.0 B support in debug m... (2)
-> + Repeating element question (2)
-> + Newly Purchased Version Not La... (2)
-> + xsl:include not finding file (5)
-> + JAXP and XSLT 2.0 / XPATH 2.0 (2)
-> + ASP:DropDownList trigger in Xs... (2)
-> + Auto-Skip empty values (2)
-> + retrieving a javascript functi... (2)
-> + need help (2)
-> + html tag ignored (2)
-> + Quick reply needed (8)
-> + xslt to remove namespaces but ... (2)
-> - Using a WSDL definition in an ... (1)
-> + XSL logic issue for simple inp... (6)
-> + Regarding XML namespace prefix... (4)
-> + Mapper reoganizes itself. (8)
-> + XSL Substring Removal (2)
-> + Regarding XSLT logic for a sim... (3)
-> + XSLT Transform documentation (2)
-> + XSLT stack trace in case of er... (3)
-> + No New Line (2)
-> - No New Line (1)
-> + howto loop through a sequence (2)
-> + xml and xsl and whitespace in... (2)
-> + XSL Date formatting (4)
-> + XSL to XSL Mapping using custo... (4)
-> + flat xml to nested xml comvers... (4)
-> + Including schema in scenario (2)
-> + DTDs and traversing (2)
-> + Help with transformation (2)
-> + Problem running XSLT against X... (2)
-> + Carriage return in the output (5)
-> + Generating XSLT to match a sch... (3)
-> + WYSIWYG editor (2)
-> + Grouping without For-Each (3)
-> + output XML using XSLT (8)
-> + Help configuring Xalan-j proce... (8)
-> + Convert Existing HTML pages to... (2)
-> + Generating Transformation - XS... (4)
-> + DOCTYPE public and system info... (2)
-> + Using EXSLT str:tokenize funct... (5)
-- Previous [661-680] [681-700] [701-720] Next
+ XQuery Help and Discussion (2017)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (364)
+ Stylus Studio Announcements (113)
Topic  
Postnext
Glenn RobertsSubject: XML Mapper Limitations
Author: Glenn Roberts
Date: 13 May 2002 10:53 AM
I am currently evaluating your product to assist our requirement to write XSLT files.

I was particularly interested in using your XML Mapper, as it may speed up development and provide "coverage" information whilst writing a transformation source file; it could also be useful to assist maintenance.

However after successfully creating an XSLT file using the XML Mapper, I wanted to improve the file to make it easier to read for maintenance purposes.

My first requirement was to insert blank lines to highlight parts of the source file. Unfortunately when I move between the XSLT source and the XML mapper tabs the source file is reformatted and blank lines are lost.

My second requirement was to break up the single template into a set of templates within the same source file. I did this and re-tested, however the mapper only displayed the links for the "root" template, and therefore only a small part of the mapping is shown. The requirement for using templates was two fold, to make it easier to understand the translation process by breaking it up into potentially re-usable parts and also to enable support a more complicated XML hierarchy.

As a more minor comment, the mapper does not show "graphically" attributes that have been defined with a fixed value; it would be nice if the Mapper did this.

My conclusions are that the XML Mapper facility cannot be used for requirements where maintainability is an issue. I am also concerned that the accidental selection of this tab would cause re-formatting which can only be recovered by avoiding saving the source file.

Is my understanding of these issues correct? Are there any enhancements in progress which will address these issues?

Postnext
Ivan PedruzziSubject: RE: XML Mapper Limitations
Author: Ivan Pedruzzi
Date: 13 May 2002 11:25 AM
Hi Glenn,


> -----Original Message-----
> From: stylus-studio-xslt Listmanager [mailto:listmanager]
> Sent: Monday, May 13, 2002 11:05 AM
> To: Recipients of 'stylus-studio-xslt' suppressed
> Subject: XML Mapper Limitations
>
>
> From: "Glenn Roberts"
>
> I am currently evaluating your product to assist our
> requirement to write XSLT files.
>
> I was particularly interested in using your XML Mapper, as it
> may speed up development and provide "coverage" information
> whilst writing a transformation source file; it could also be
> useful to assist maintenance.
>
> However after successfully creating an XSLT file using the
> XML Mapper, I wanted to improve the file to make it easier to
> read for maintenance purposes.
>
> My first requirement was to insert blank lines to highlight
> parts of the source file. Unfortunately when I move between
> the XSLT source and the XML mapper tabs the source file is
> reformatted and blank lines are lost.

You should use XML comment like

(!-- my comment -->

they will be preserved and will not affect your output

>
> My second requirement was to break up the single template
> into a set of templates within the same source file. I did
> this and re-tested, however the mapper only displayed the
> links for the "root" template, and therefore only a small
> part of the mapping is shown. The requirement for using
> templates was two fold, to make it easier to understand the
> translation process by breaking it up into potentially
> re-usable parts and also to enable support a more complicated
> XML hierarchy.

Select the link, right click on it and choose "Properties", a docking
window will appear. The last line is "Uses Template" if you change the
value to True Mapper will generate named template for you

Hope this helps

Ivan Pedruzzi
eXcelon Corporation
http://www.stylusstudio.com


>
> As a more minor comment, the mapper does not show
> "graphically" attributes that have been defined with a fixed
> value; it would be nice if the Mapper did this.
>
> My conclusions are that the XML Mapper facility cannot be
> used for requirements where maintainability is an issue. I
> am also concerned that the accidental selection of this tab
> would cause re-formatting which can only be recovered by
> avoiding saving the source file.
>
> Is my understanding of these issues correct? Are there any
> enhancements in progress which will address these issues?
>
>
>
> To reply: mailto:stylus-studio-xslt.5073@edn.exceloncorp.com
> To start a new topic: mailto:stylus-studio-xslt@edn.exceloncorp.com
> To login: http://edn.exceloncorp.com/~SSDN
>
>

Postnext
Glenn RobertsSubject: RE: XML Mapper Limitations
Author: Glenn Roberts
Date: 13 May 2002 12:48 PM
Thank you for your prompt response.

Both suggestions worked and satisfy my main requirements (I would have liked to add blank lines; but I can now at least put comments in important "code" sections).

I guess (I'm a novice at XSLT) for simple requirements the following code generated by the mapper:





is functionally equivalent to



Apart from these problems, I am very impressed with the product so far.
Postnext
Glenn RobertsSubject: RE: XML Mapper Limitations
Author: Glenn Roberts
Date: 13 May 2002 12:49 PM
Thank you for your prompt response.

Both suggestions worked and satisfy my main requirements (I would have liked to add blank lines; but I can now at least put comments in important "code" sections).

I guess (I'm a novice at XSLT) for simple requirements the following code generated by the mapper:

\
\
\

is functionally equivalent to

\

Apart from these problems, I am very impressed with the product so far.
Posttop
Glenn RobertsSubject: RE: XML Mapper Limitations
Author: Glenn Roberts
Date: 13 May 2002 12:51 PM
Thank you for your prompt response.

Both suggestions worked and satisfy my main requirements (I would have liked to add blank lines; but I can now at least put comments in important "code" sections).

I guess (I'm a novice at XSLT) for simple requirements the following code generated by the mapper:

xsl:for-each select="xxx"
xsl:call-template name="xxx-xxx"
xsl:for-each

is functionally equivalent to

xsl:apply-templates select="xxx"

Apart from these problems, I am very impressed with the product so far.

SORRY FOR THE REPETITION - I couldn't make the email pass through the xsl tags.
   
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.