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 » XSL switching stylesheet from v1.0 to v2.0
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
- Stylus Studio Technical Forum (14621)
-> - UV Kit (1)
-> - Preview PDF as HTML? (1)
-> + ArrayIndexOutOfBoundsException... (3)
-> + WSCC to KML transform help (5)
-> + Using XSV 3.1-1 as an external... (2)
-> + Cannot debug stylesheet (2)
-> + Error installing Stylus Studio... (3)
-> - Windows XP "not responding" er... (1)
-> - Windows XP "not responding" er... (1)
-> + HTML to XSL (2)
-> + Run Stylus studio from command... (2)
-> + Setting Context for XPath Quer... (5)
-> + Batch process to check well-fo... (9)
-> + WSDL validator? (8)
-> - How to be still using Old Jars (1)
-> - Install Stylus Studio on anoth... (1)
-> + Install Stylus Studio on anoth... (3)
-> + How to validate via catalog lo... (4)
-> + New Installation Upgrade Issue... (4)
-> - Freelance Project - Mapping di... (1)
-> + Converting from Edifact to SQL... (3)
-> + converting data file to xml us... (2)
-> + have serious problem with Styl... (2)
-> + ddtek:sql-delete (3)
-> + Web Service Call with Axis: No... (3)
-> + Entity gets replaced when inde... (2)
-> + EDIFACT import error (3)
-> + (401) forbidden error (8)
-> + Error when data type not speci... (2)
-> - Globally delete duplicates of ... (1)
-> + Validation too slow!!!! (4)
-> + Define a complex type with mul... (2)
-> + XML Playlists (2)
-> - Create SOA Web Service with me... (1)
-> + Spell checking?? (2)
-> - saxon 9 linebreak in text mode (1)
-> + Apache FOP gets NoClassDefFoun... (3)
-> + Nillable Decimal (4)
-> + Transform XML to AS400 Databas... (4)
-> + xs3p vs xsDoc (3)
-> + Update Installation Problem (11)
-> + Java Heap error and -Xmx param (5)
-> + 2007 Pro won't run XSL files c... (3)
-> + access to multiples databases ... (6)
-> + License Authentication Failed (2)
-> + XSLT Mapper: How to aggregate ... (2)
-> + Why my WYSIWYG tab disappeared... (3)
-> + Flat File (From mainframe COBO... (9)
-> + X12 Validation (5)
-> + Schema replacement in Microsof... (2)
-> + [OT] XML fragment - error expl... (3)
-> + Re-using a simple type definit... (2)
-> + What is "Java bult-in" XSLT Pr... (2)
-> + Error when generating .NET cod... (6)
-> + options for sum(function) - to... (2)
-> + [OT] XSD - is this valid XML o... (2)
-> + Multiple page sequences (2)
-> + License disabled (3)
-> + EDIFACT to XML with multiple Q... (5)
-> + Viewing Web Service Call http ... (2)
-> - keyref handling by different p... (1)
-> + Running transform in SS UI com... (9)
-> + Mapping from one schema to ano... (3)
-> - Using document() to lookup fro... (1)
-> + Can not open a xml file in IE ... (2)
-> + Stylus Studio detected a chang... (3)
-> + Customer Support for Stylus St... (2)
-> + WebService Call is not working... (3)
-> + Activation Problem (2)
-> + Activating Stylus Studio 2008 (3)
-> + Cannot use UNC paths, get save... (22)
-> + DB to XML Data Source not avai... (3)
-> + Stylus Studio 2008 Installatio... (16)
-> - SQL Server 2005 xml datatype -... (1)
-> + XML Reporting: linking to sect... (4)
-> + Merge an external xml with inp... (4)
-> + Stylus Closing abruptly (4)
-> + Best approach for generating X... (2)
-> + Problem with Java call (5)
-> + Changing the top margin (2)
-> + Generating a Web Service Call (2)
-> + import xml into excel using V... (2)
-> + FOP producing NoSuchMethodErro... (6)
-> + Reporting Errors (2)
-> + Doc/Literal Wrapped (2)
-> + Need image to render at higher... (3)
-> + HTML to xml wizard on thousand... (2)
-> + Doc/Literal and SOAP Header/Bo... (2)
-> - Help with settping up MS Acces... (1)
-> + WSDL - A Well Defined Service (7)
-> + XML to XML Mapping - Combining... (2)
-> + CData Question (3)
-> + mySQL DB Connection (11)
-> + XPath documentation confusion (2)
-> + Extra block/CR generated (6)
-> + Apache FOP (2)
-> + Inserting Java Script (2)
-> + Convert EDIFACT to X12 or vice... (6)
-> + XSD: Restricting an attribute ... (2)
-> + Creating dynamically named ele... (2)
-- Previous [1201-1220] [1221-1240] [1241-1260] 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
roberto azzimontiSubject: XSL switching stylesheet from v1.0 to v2.0
Author: roberto azzimonti
Date: 11 Oct 2007 12:46 PM
Originally Posted: 11 Oct 2007 12:45 PM
I'm using Stylus 2007 enterprise suite release 2 build 894m on Windows XP professional.

The XSL I'm testing was working fine.
When I changed the stylesheet version from 1.0 to 2.0 I started to get some errors. Switching back from v2.0 to v1.0 the error were still there. I wasted a lot of time trying to figuring out what was going on. Finally I realized the information that Stylus attached to the bottom of the XSL did not change or reset when I switched back from v2.0 to v1.0
I manually deleted those information and reset my project, finally I got my XSL to work again.

Please advise or fix this bug asap as it's very annoying and missleading for debugind XSL.
Thanks.
Postnext
Ivan PedruzziSubject: XSL switching stylesheet from v1.0 to v2.0
Author: Ivan Pedruzzi
Date: 11 Oct 2007 01:56 PM
Ciao Roberto,

What kind of error you got when version was set back to "1.0"?

Stylus Studio doesn't store any XSLT version in the meta-information fragment but just the scenario settings: processor, input XML, output, etc.

Thanks for you help.
Ivan Pedruzzi
Stylus Studio Team
Postnext
roberto azzimontiSubject: XSL switching stylesheet from v1.0 to v2.0
Author: roberto azzimonti
Date: 11 Oct 2007 02:07 PM
ciao Ivano,

Here some more info:

We are actually using this declaration in ordet to be able to use node-set:

<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:exsl="urn:schemas-microsoft-com:xslt"
extension-element-prefixes="exsl">

When switched to v2.0 setting stored on the bottom of the XSL were set to use different processors, swicthing back to v1.0 those settings did not change. From that point on we were getting invalid parameter for node-set at this line:

<xsl:variable name="ThisNode" select="(exsl:node-set($SortedPSRNodes)/*)[$NodeSetCount]"/>

Hope this help otherwise we can try to duplicate the problem sending you a step by step actions and a sample too if necessary.

Grazie.

Postnext
Ivan PedruzziSubject: XSL switching stylesheet from v1.0 to v2.0
Author: Ivan Pedruzzi
Date: 11 Oct 2007 02:33 PM

Actually my name is Ivan without the final o.

Here is what happened:

Your XSLT is using {urn:schemas-microsoft-com:xslt}node-set, a Microsoft proprietary extension function.

When you switched to XSLT 2.0 Stylus Studio prompted you to switch to Saxon, the only processor that supports XSLT 2.0.

Saxon raised an error because didn't recognized the node-set function so you switched back to XSLT 1.0 but you were still running with Saxon therefore you got the same error again.

The solution is pretty simple and doesn't require to touch the the meta info. Click on the toolbar button "..." and set the processor back to one of the Microsoft one.

Hope this helps
Ivan







Ivan Pedruzzi
Stylus Studio Team
Postnext
roberto azzimontiSubject: XSL switching stylesheet from v1.0 to v2.0
Author: roberto azzimonti
Date: 11 Oct 2007 02:45 PM
I did that,
didn't work,
I compared my settings with a Stylus a colleque of mine was using and realized that the processor was different, so I tried Built-in (my usual default) and the Microsoft ones. None of them worked until I manually deleted the note on the bottom of the XSL which was still reporting Saxon, then reloading the XSL started to work.

PS
I added the "o" for a more Italian sound..
Postnext
roberto azzimontiSubject: XSL switching stylesheet from v1.0 to v2.0
Author: roberto azzimonti
Date: 11 Oct 2007 02:53 PM
to be picky,
you should save the settings for v1.0 so when switching back Stylus would actually restore your original setting for v1.0 otherwise we don't know exactly what changed in the settings therefore we can not manually reset them.
Postnext
Ivan PedruzziSubject: XSL switching stylesheet from v1.0 to v2.0
Author: Ivan Pedruzzi
Date: 11 Oct 2007 03:20 PM

When trying to run XSLT 2.0 with a 1.0 processor you get the following message, therefore Stylus Studio makes you aware on what is changing.

---------------------------
Stylus Studio 2007 XML Enterprise Suite
---------------------------
The selected XSLT processor is not compatible with XSLT 2.0.

Do you want to use the Saxon processor instead?
---------------------------
Yes No Cancel
---------------------------

One thing we could do is to force you change the processor manually bu it sounds more unfriendly.

In addition switching XSLT version is not like changing an external parameter value, you are changing the transformation language, it makes no sense for us to preserve the settings for different version of the XSLT source.
Postnext
roberto azzimontiSubject: XSL switching stylesheet from v1.0 to v2.0
Author: roberto azzimonti
Date: 11 Oct 2007 04:27 PM
agree with your above statement (I forgot about the warning message).

However, even if I set a different processor I still get the error, here are the steps to reproduce the problem:

1.) Changed to v2,.0
2.) Got warning about using saxon, I chose yes
3.) Got error about node-set during debugging
4.) Changed back to v1.0
5.) Options still says Built-in processor
6.) Tried to set any other processors in the option panel still getting node-set error
7.) Manually removed matainfo section, now it works.

Here how the metainfo looks like (processortype still set to "saxon8"):

<!-- Stylus Studio meta-information - (c) 2004-2007. Progress Software Corporation. All rights reserved.
<metaInformation>
<scenarios ><scenario default="yes" name="Scenario1" userelativepaths="yes" externalpreview="no" url="ExportXMLPSR.xml" htmlbaseurl="" outputurl="" processortype="saxon8" useresolver="yes" profilemode="0" profiledepth="" profilelength="" urlprofilexml="" commandline="" additionalpath="" additionalclasspath="" postprocessortype="none" postprocesscommandline="" postprocessadditionalpath="" postprocessgeneratedext="" validateoutput="no" validator="internal" customvalidator=""/></scenarios><MapperMetaTag><MapperInfo srcSchemaPathIsRelative="yes" srcSchemaInterpretAsXML="no" destSchemaPath="" destSchemaRoot="" destSchemaPathIsRelative="yes" destSchemaInterpretAsXML="no"/><MapperBlockPosition></MapperBlockPosition><TemplateContext></TemplateContext><MapperFilter side="source"></MapperFilter></MapperMetaTag>
</metaInformation>
-->
Postnext
Ivan PedruzziSubject: XSL switching stylesheet from v1.0 to v2.0
Author: Ivan Pedruzzi
Date: 11 Oct 2007 04:37 PM
Roberto, you didn't change the processor for your XSLT document but the global settings for the default processor (Tools -> Options -> XSLT Editor -> Processor Settings)

What I described before is to click on the document toolbar button labeled "..." then click on the processor tab.


Hope this helps
Ivan Pedruzzi
Stylus Studio Team
Posttop
roberto azzimontiSubject: XSL switching stylesheet from v1.0 to v2.0
Author: roberto azzimonti
Date: 11 Oct 2007 04:48 PM
AHHHHH..
I thought they were doing exactly the same functionality no matter which one you choose to change the processor.

I understand now,

Thank you very much especially for the fast response, I like your customer support!
   
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.