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 » Stylus Studio Technical Forum » Report Designer mistakenly generates XSLT 2.0/XPath 2.0
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
- Stylus Studio Technical Forum (14621)
-> + Error in Stylus Studio - canno... (2)
-> + Saxon Assign (2)
-> - License Authentication Failed (1)
-> + Stylus Studio 2007 Download (2)
-> + EDI to XML validation (2)
-> + Reports: can't remove "undead"... (3)
-> + Document Wizard Incomplete (6)
-> + Opening xml converter (4)
-> + Node depth limit with MySQL? (5)
-> + Basics (2)
-> - Node depth limit with MySQL? (1)
-> + Creating an XML Schema from a ... (4)
-> - Issue with XSD (1)
-> + XSL-FO and Apache FOP (2)
-> + How Come Stylus Studio Fails T... (6)
-> + no suitable driver (8)
-> + 211,19: no declaration found f... (6)
-> - Validate HEX (1)
-> + Crashing when connected to dat... (3)
-> - Interface with quickbooks (1)
-> - CDATA control (1)
-> + [resolved] Namespace (and pref... (5)
-> - Hiding and Revealing Child Nod... (1)
-> + Cannot see values in Watch whe... (4)
-> - Help with CSV to XML and Regio... (1)
-> + How do I verify "opt=yes" URI ... (4)
-> - Stylus Studio claims xsd is in... (1)
-> + Can a generated XSD be used in... (4)
-> + I am not a developer I'm just ... (2)
-> + Stylus crash when deleting dat... (6)
-> - Preserving Structure (1)
-> - Preserving Structure (1)
-> - HL7 ORU group tags (1)
-> + Fixed Length Record Layout to ... (2)
-> + WebService Connect (6)
-> - WebService conection problems (1)
-> + Could not detect EDI dialect a... (3)
-> + I am a bookkeeper not a progra... (2)
-> + fatal error (4)
-> - Saxon linebreak (1)
-> + task scheduler (2)
-> - Number of Elements in Grid vie... (1)
-> + Compile Java (2)
-> + What happened to the EDI Wizar... (15)
-> + setting Transformer for java b... (3)
-> + XML Schema Documentation Gener... (3)
-> + EANCOM xsd-files (4)
-> + Failure of CDATA converting pr... (4)
-> + XML File created from text fil... (3)
-> + After purchase AND activation ... (2)
-> + XQuery Format of XML code snip... (4)
-> + Error during conversion (9)
-> - testing for empty nodes (1)
-> + edi converter - java fails (10)
-> + ddtek:serialize (3)
-> - File explorer view (1)
-> - Java Extension Functions (1)
-> + err:FODC0004 (18)
-> - Removing Attributes when Null (1)
-> + CDATA preservation (6)
-> + Help converting xml report to ... (2)
-> + Converting text to XML issue (3)
-> - example not working (1)
-> + XML Editing (2)
-> + Multiple EDI messages within s... (5)
-> + Mapping RDBMS and XML Schema t... (2)
-> + MySQL Database importing (2)
-> + XSD validation using XSV fails... (3)
-> + Is this really well-formed? (3)
-> + HL7 EDI to XML problems -'ORU_... (11)
-> + How do I modify the Xquery to ... (2)
-> + XML mapping difficulty (3)
-> + XLST Conversion (2)
-> + HTML TO XSL Conversion (2)
-> - Convert an EBCDIC file to XML (1)
-> + License Manager still indicate... (4)
-> + Still sometimes getting beat b... (2)
-> + What versions of MySQL are sup... (5)
-> - External XSLT processor proble... (1)
-> + DDEE0082 Erro Internal system ... (6)
-> + Calling function from .NET C# (2)
-> + Stylus studio projects bound t... (3)
-> - Report Designer mistakenly gen... (3)
-> ->Report Designer mistakenl...
-> ->Report Designer mistakenl...
-> + Choose Nodes in pipelines (3)
-> + Custom external processor and ... (2)
-> + predefined (4)
-> + translate function in java (2)
-> + XMLPipeline trouble in Linux (7)
-> + Converting Custom EDI Message ... (2)
-> + tab delimetered file with vari... (2)
-> + XML validation with XSD (2)
-> + Missing documentation: SSL_Cer... (2)
-> + Parse Xcel input file which is... (2)
-> + XML Publisher post processors (2)
-> + Alignment of table items in XM... (2)
-> + XML to PDF using XML Publisher (2)
-> + Blurry Background image / Vect... (4)
-> + URIResolver error on command l... (2)
-> + stylus studio - the (3)
-> + problem with omit from output ... (3)
-- Previous [481-500] [501-520] [521-540] Next
+ Website Feedback (249)
+ XSLT Help and Discussion (7625)
+ XQuery Help and Discussion (2017)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (364)
+ Stylus Studio Announcements (113)
Topic  
Postnext
Yitzhak KhabinskySubject: Report Designer mistakenly generates XSLT 2.0/XPath 2.0
Author: Yitzhak Khabinsky
Date: 21 Apr 2010 07:38 AM
This is a repost for the old issue:

http://www.stylusstudio.com/SSDN/default.asp?action=9&read=8995&fid=48

Stylus Studio 2010 (build 1540b) Report Designer generates XSLT 2.0/XPath 2.0 inline “if” statements even upon selection XSLT 1.0 in the Report>Generate> (selecting Transformation Language : XSLT 1.0).

Every time a change is made to the report, you have to regenerate the XSLT, and make manual change converting inline "if"s to XSLT 1.0.

Please take a look into this issue.
It seems like a bug.

Regards,
Yitzhak
Postnext
(Deleted User) Subject: Report Designer mistakenly generates XSLT 2.0/XPath 2.0
Author: (Deleted User)
Date: 21 Apr 2010 12:15 PM
Hi Yitzhak,
do you have an example of when XML Report generated an "if()" statement even when XSLT 1.0 was selected? For instance, in the thread you linked the statement was manually entered by the user, and that is outside the control of XML Report.

Thanks,
Alberto
Posttop
Yitzhak KhabinskySubject: Report Designer mistakenly generates XSLT 2.0/XPath 2.0
Author: Yitzhak Khabinsky
Date: 21 Apr 2010 02:18 PM
Hi Alberto,

You are absolutely correct – the XPATH statement is typed manually. So when SS Report Designer generates XSLT it emits the XPath property verbatium. Eventually, we are using .NET XslCompiledTransform Processor plus an XML file to generate final FO file. Obviously, .NET Processor (XSLT 1.0/XPath 1.0 compliant) cannot process XSLT 2.0/XPath 2.0 and fails.

When grid needs alternate background colors for even and odd rows SS Report Designer supports it. To do that in the SS Report Designer there are properties settings (typed manually) for the row as follows:
Background: <dynamic>
Context: $WorkInfoRow
XPath: if(position() mod 2 = 1) then "white" else "lightsteelblue"

Now I am trying to generate the XSLT using :
Report>Generate> (selecting Transformation Language : XSLT 1.0)
Unfortunately, the generated XSLT is compliant with XSLT 2.0/XPath 2.0 which allows inline “if” statements”
<fo:table-row background-color="{if(position() mod 2 = 1) then &quot;white&quot; else &quot;lightsteelblue&quot;}">

Because of such behavior, I have to manually go to the generated XSLT and change it every single time to make it compliant with the XSLT 1.0.

<xsl:variable name="ColorW">
<xsl:choose>
<xsl:when test="position() mod 2 = 0">white</xsl:when>
<xsl:otherwise>lightsteelblue</xsl:otherwise>
</xsl:choose>
</xsl:variable>
<fo:table-row background-color="{$ColorW}">

Regards,
Yitzhak
   
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.