XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
- Stylus Studio Technical Forum (14621)
-> - Stylus Studio - Registrar en o... (1)
-> + Stylus Studio - Registrar en o... (2)
-> + Can a pipeline send a file by ... (2)
-> + After Updateing WIN10 to WIN11... (12)
-> + Where do I add the custom java... (3)
-> + Where is the Diagram tab? (5)
-> + Applying XSLT to Word DOCX/XML (2)
-> - CSV conversion via ConvertToXM... (1)
-> + Text symbols in SS not same as... (4)
-> + Exposing xquery as webservice ... (6)
-> + Syntax Identifier (2)
-> + Saving a Converted XML as an X... (5)
-> + Output document cannot be pars... (4)
-> - Archiving output from conversi... (1)
-> + EDIFACT guideline from Stylus ... (3)
-> + CSV file putting all the data ... (5)
-> + Can't install Home version 64b... (5)
-> + presale - Can I covers this sc... (5)
-> + Problem with UNB (5)
-> + Splitting EDIFACT files pipeli... (4)
-- [1-20] [21-40] [41-60] 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
Max HodgesSubject: Node-set function namespace for built-in processor
Author: Max Hodges
Date: 08 Jun 2001 02:35 AM
Is there a node-set extension function for the built in processor?

If I use the msxml:node-set() function, then I cannot debug my style sheet in Stylus Studio.

Is there a node-set function I can use for the built-in processor, so I can debug in Stylus? What is the namespace?

Thanks,
Max Hodges
www.jobdragon.com
Tokyo

Postnext
Minollo I.Subject: Re: Node-set function namespace for built-in processor
Author: Minollo I.
Date: 11 Jun 2001 12:54 PM
At 02:39 AM 6/8/2001 -0400, you wrote:
>From: "Max Hodges"
>
>Is there a node-set extension function for the built in processor?
>
>If I use the msxml:node-set() function, then I cannot debug my style sheet
>in Stylus Studio.
>
>Is there a node-set function I can use for the built-in processor, so I
>can debug in Stylus? What is the namespace?

Max,
in XSLT 1.0 there isn't any function that allows you to convert a result
tree fragment into a node set; that's something I would consider a hole in
the 1.0 specifications, that MS has tried to fix with the non standard
node-set() function.
In Stylus Studio we are moving in the direction of supporting this in a way
similar to what XSLT 2.0 is going to do, that is giving you the possibility
to apply node-set operations to a result tree fragment (RTF as a data type
is actually disappearing in XSLT 2.0); this functionality has been in our
plans for a while, and recently we have started work on it; as soon as a
build exposing this feature is available, we'll let you know.

Thanks for your feedback,
Minollo

Posttop
Minollo I.Subject: Re: Node-set function namespace for built-in processor
Author: Minollo I.
Date: 11 Jun 2001 05:04 PM
Max,
you will happy to know that I've checked about the status of this issue,
and the desired behavior is already available in build 43, which is the
latest version currently available.

So, using build 43, if you declare a variable declared like this:
<xsl:variable name="var"> <a att="1"/>
<a att="2"/> <a att="3"/>
</xsl:variable>
....using MSXML you would loop on all the a's doing:
<xsl:for-each select="msxsl:node-set($var)/a">
Using Stylus Studio you do:
<xsl:for-each select="$var/a">

Hope this helps,
Minollo

   
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.