This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Node-set vs. Result tree fragment
- To: xsl-list at mulberrytech dot com
- Subject: Node-set vs. Result tree fragment
- From: "Michael J. Hudson" <mhudson at blueprinttech dot com>
- Date: Mon, 10 Jul 2000 17:10:22 -0400
- CC: xsl-list-digest at mulberrytech dot com
- Organization: Blueprint Technologies, Inc.
- References: <200007101818.OAA08656@mulberrytech.com>
- Reply-To: xsl-list at mulberrytech dot com
Newbie question:
What exactly is the difference between a node-set and result tree
fragment. If I have a node-set, will I be able to access the children
of the nodes in that node-set?
I tried writing a XSLT script that called a Java method and as a
parameter send a node-set to that Java method. Now, I know this
all varies from one processor to another... but I wasn't able to
obtain the children of the node I passed into the Java method...
just the node itself. I was using the Lotus XSLT processor... and
am wondering if there is a way to pass a node-set or a result tree
fragment so that I can access both the top nodes as well as its
children.
Is that what the node-set extensions in XT and such are for?
-------------------------------------
Michael J. Hudson
Software/Framework Engineer
mhudson@blueprinttech.com
cell-phone: 703.362.8039
voice-mail: 703.827.0638 ext. 4786
fax: 703.734.0987
Blueprint Technologies
"The E-Solution Architect"
http://www.blueprinttech.com
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list