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 » XSLT Debug Call Stack doesn't always pop stack - call-template calls seem to be an issue
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
- Stylus Studio Technical Forum (14621)
-> + What Pipeline standard do you ... (4)
-> + How can i increase sylus memor... (2)
-> - Tutorial & Tech support needed (1)
-> + Generate HTML Documentation fr... (3)
-> + Use of saxonsa outside stylus ... (2)
-> + Schema to DTD (6)
-> + Trial version requires interne... (4)
-> - APACHE FOP text box (1)
-> + Cannot create SQL Server datas... (11)
-> + StylusValidator Crashes (2)
-> + XML diff with optimize Change ... (2)
-> + how do I get the .xsl page to ... (3)
-> + Can't Use WYSIWYG from the Fil... (6)
-> + EDI Help (2)
-> + XInclude support (3)
-> + Editor options and customized ... (3)
-> + Licensed version connectes to ... (6)
-> + handling abstract types in the... (5)
-> + XML not validating against its... (4)
-> + SS gets into state where the "... (6)
-> + Download Link from Order email... (2)
-> + Stylus Studio doesn't run (2)
-> + Indent XML Tags uses pretty sh... (2)
-> + Some questions on supported pl... (3)
-> + Apache FOP Border (2)
-> + line numbers, line-wrap.. (11)
-> + Not Able to Load Siebel Web Se... (3)
-> + XSLT node or nodeset as scenar... (4)
-> - tree view parsing error: Expec... (1)
-> + reactivating the license key f... (2)
-> + XSL FO region-body border (2)
-> + WhiteSpace facet default (2)
-> - Web Service Call (1)
-> + DB to XML convertion (6)
-> + Converting: How to handle data... (2)
-> + Toss Character Exception (2)
-> + EDI conversion COM segment (5)
-> - SS passing invalid CALS table ... (1)
-> + Carrier Related EDI SAP questi... (2)
-> + How to generate 1 output XML f... (2)
-> + Urgent Eval: How2 w/ Possibly ... (4)
-> + Preview Problems (7)
-> + Mapping to EDIFACT ORDERS UNT0... (8)
-> + Deploying Conversion XML to ED... (2)
-> + Use EDI Adapter within Sap BC (3)
-> + Uninstall->instal entepr. 2007 (2)
-> - xml data to sql 2000 table (1)
-> - Convert from Oracle DB to XML ... (1)
-> + NTFShardlink broken (5)
-> + Can't get catalog to work (3)
-> + Only One of each EDI segment g... (3)
-> + convert (2)
-> + convert (4)
-> + EDIFACT to XSD problem (3)
-> + quark xpress tags (2)
-> + Duplicating nodes allows to cr... (2)
-> + Duplicated, unused nodes are r... (3)
-> + Converting to XML from a varie... (5)
-> + xsd:import's with escaped char... (8)
-> + Viewing the FO Sample Applicat... (3)
-> + Stylus Studio - Window tiling (3)
-> + Question about XML->Java Objec... (2)
-> + SVG web-based editor (2)
-> + conversion process for the pdf... (2)
-> + GUI Mapper does not create pro... (4)
-> + JavaScript working inside prev... (4)
-> + Stylus Studio Crashes when I a... (4)
-> + SVG ImageReader for FOP (2)
-> + Web Service Call Using HTTPS (8)
-> + Meditech database (2)
-> + How to connect to Informix (5)
-> + long filenames in Berkeley XML... (3)
-> + Opening multiple documents = m... (3)
-> + MySQL Connectivity (2)
-> + using .xsd to create forms (3)
-> + Convert-to-XML Engine could no... (2)
-> + editor questions (2)
-> + Cannot connect to SQL server (7)
-> + Convert Cobol file to XML (2)
-> + XML Diff problem (4)
-> + running XSLT - time + memory m... (7)
-> + New wsdl creation (4)
-> + DB to XML Parameters (2)
-> + Help (html in xml) need to out... (8)
-> + Stylesheet questions (2)
-> + Verion 1.0 XPATH for testing "... (5)
-> + Berkely XML DB file system (2)
-> + WYSIWYG in 2007 demo (2)
-> + EDIFACT code list problem (3)
-> + XQuery over a Berkeley XML DB ... (3)
-> + Href and display linked ref. (2)
-> + How my applications can gener... (11)
-> + CLASSPATH (2)
-> + Fixed order of attributes (2)
-> + merging XML files (13)
-> - The Struzzo.exe hung with no G... (1)
-> + Problem Registering Old Versio... (4)
-> + CHART.XML + CHART.XSL to CHART... (17)
-> + Aplication not loading (6)
-> + Can Stylus Studio be used to s... (2)
-- Previous [1801-1820] [1821-1840] [1841-1860] 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
Andy GalvanSubject: XSLT Debug Call Stack doesn't always pop stack - call-template calls seem to be an issue
Author: Andy Galvan
Date: 08 Aug 2006 03:32 PM
I'm running Stylus StudioŽ 2006 Release 2 Build 591d. When I debug an XSLT, the Call Stack seems to accumulate templates that have been called, but which have subsequently ended. I suspect the call-template with embedded apply-template commands somehow confuses the call stack. Is anyone else having a similar problem?
Postnext
Ivan PedruzziSubject: XSLT Debug Call Stack doesn't always pop stack - call-template calls seem to be an issue
Author: Ivan Pedruzzi
Date: 08 Aug 2006 06:02 PM
Hi Andy,

If you post an example we will try to reproduce it here

Thank You
Ivan Pedruzzi
Stylus Studio Team
Postnext
Andy GalvanSubject: XSLT Debug Call Stack doesn't always pop stack - call-template calls seem to be an issue
Author: Andy Galvan
Date: 08 Aug 2006 06:10 PM
I've created a very simple XSLT that calls and applys templates. If you debug this and stop at the 'Begin' element, the Call Stack shows the match="/" template at line 5.

If you continue and stop again at the 'End' element, the Call Stack shows, "/" (line 6), "A" (line 14), "Called Template1" (line 18), "B" (line 23), "Called Template2" (line 27), and "B" (line 7).

I expected the same Call Stack as the first stop, match="/"


ApplicationSample(7).xsl
Sample XSLT

DocumentSample(8).xml
sample input for XSLT
Postnext
Ivan PedruzziSubject: XSLT Debug Call Stack doesn't always pop stack - call-template calls seem to be an issue
Author: Ivan Pedruzzi
Date: 08 Aug 2006 06:22 PM

The latest build (653e) works fine, I will try 591d as well.

Which XSLT processor are you running?

Ivan
Postnext
Andy GalvanSubject: XSLT Debug Call Stack doesn't always pop stack - call-template calls seem to be an issue
Author: Andy Galvan
Date: 08 Aug 2006 06:43 PM
Originally Posted: 08 Aug 2006 06:24 PM
Microsoft .Net 1.x

Ah... I see that the built in processor works OK. So the Microsoft .Net 1.x processor must be the issue.

Also, the Watch Window doesn't work properly with the Microsoft .Net 1.x processor... try stopping at <xsl:element name="In">. Then, try to "Watch" C or D. I get values with the built in processor, but not with the Microsoft .Net 1.x processor.

I really need to use the Microsoft .Net 1.x processor, since that's the processor that will be used in our production application.

Postnext
Ivan PedruzziSubject: XSLT Debug Call Stack doesn't always pop stack - call-template calls seem to be an issue
Author: Ivan Pedruzzi
Date: 08 Aug 2006 07:05 PM
That explains it! we discovered many issues running System.Xml.XslTransform in debug mode.

If you need to check the flow of your stylesheet you can use built-in or Saxon then run .NET to verify the final result.

Hope this helps
Ivan Pedruzzi
Stylus Studio Team
http://www.stylusstudio.com/xml_download.html
Postnext
Andy GalvanSubject: XSLT Debug Call Stack doesn't always pop stack - call-template calls seem to be an issue
Author: Andy Galvan
Date: 10 Aug 2006 12:29 PM
Ivan, thanks for acknowledging the issue and offering a short term solution. I do have some stylesheets that require the Microsoft .Net 1.x processor because of msxsl (VB) scripts. These are hard to debug, as it is, and eliminating the Microsoft processor makes it just that much more difficult.
I'm unclear as to the long term resolution. Is this not considered a bug, and something that SS will be fixing?
And what about Microsoft .Net 2.x processor? We will soon be moving to that as a corporate standard for all our applications. What is the SS direction for supporting the Debug feature, using a Microsoft .Net 2.x processor?
Postnext
Ivan PedruzziSubject: XSLT Debug Call Stack doesn't always pop stack - call-template calls seem to be an issue
Author: Ivan Pedruzzi
Date: 11 Aug 2006 09:22 AM

Why are you forced to use script extensions?

Add support for debugging XslCompiledTransform is in our radar but there is no firm plan yet.

Ivan Pedruzzi
Stylus Studio Team
Postnext
Andy GalvanSubject: XSLT Debug Call Stack doesn't always pop stack - call-template calls seem to be an issue
Author: Andy Galvan
Date: 11 Aug 2006 09:39 AM
I needed the current date-time and a GUID. These had to be added to the output xml file during the transform process. I found the VBscript to be the easiest to accomplish this.
Postnext
Ivan PedruzziSubject: XSLT Debug Call Stack doesn't always pop stack - call-template calls seem to be an issue
Author: Ivan Pedruzzi
Date: 11 Aug 2006 09:46 AM

You could pass those as parameters to the stylesheet

Ivan
Postnext
Andy GalvanSubject: XSLT Debug Call Stack doesn't always pop stack - call-template calls seem to be an issue
Author: Andy Galvan
Date: 11 Aug 2006 09:54 AM
That's what I originally suggested... but based on the isolated need and wide distribution support of the calling web service, it was deemed "my problem". So, I have a several XSLTs in my arsenal that use VB scripts.
Postnext
roberto azzimontiSubject: XSLT Debug Call Stack doesn't always pop stack - call-template calls seem to be an issue
Author: roberto azzimonti
Date: 11 Aug 2006 12:12 PM
I'm evaluating your Stylus Studio 2006 Enterprise edition 653e.
I also found a (major) problem for us running transformation in debug mode. The order we process the records is crocial. Your product seems to stack lists in reverse order. Consider this fragment of code:

<xsl:variable name="sumBit">
<xsl:call-template name="elem">
<xsl:with-param name="thisNode" select="key('detail-by-uid', $thisKey)[1]/adjustment/item[@name=$attrBit]"/>
</xsl:call-template>
</xsl:variable>

In your editor the node passed to the template is the last one in the list even if we hard-coded position [1]. If we use last() the node passed is actually the first one in the list. We can not use your editor if this is its standard behavior.

Please, advice.
Thanks.
Posttop
Minollo I.Subject: XSLT Debug Call Stack doesn't always pop stack - call-template calls seem to be an issue
Author: Minollo I.
Date: 11 Aug 2006 03:42 PM
Roberto,
we are able to reproduce this problem, and we have a fix for it; the fix will be part of the next Stylus Studio update, but in the meanwhile we can make it available to you if this is a show stopper in your evaluation; please contact us at stylus-field-report@progress.com if you are interested in a module patch.

Thanks.
   
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.