This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Node-set vs. Result tree fragment
- To: xsl-list at mulberrytech dot com
- Subject: Re: Node-set vs. Result tree fragment
- From: "Michael J. Hudson" <mhudson at blueprinttech dot com>
- Date: Tue, 11 Jul 2000 13:53:34 -0400
- CC: xsl-list-digest at mulberrytech dot com
- Organization: Blueprint Technologies, Inc.
- References: <200007111502.LAA07924@mulberrytech.com>
- Reply-To: xsl-list at mulberrytech dot com
> Mike Kay wrote:
> The way I read the question, the answer is yes. If you have a nodeset $ns,
> you can access the children of the nodes in $ns by writing $ns/node() (or
> $ns/* if you only want the element children, or $ns/para if you only want
> the <para> element children, etc).
>
> What you can do in an extension function depends on the implementation.
> Certainly with Saxon, when you pass a node-set to an extension function
> there are methods to navigate from any node to its children, siblings,
> parent, etc.
>
> The node-set() extension function is there to make result tree fragments
> navigable in the same way that node-sets are.
Well, then here's a question in regards to this then...
I wrote an XSLT script a while back that called a Java method and passed
a node-set to it. From within the Java program, I could only get the
actual
nodes in that node-set, not any of those node's childrens.
Is programmable DOM parsing of a node-set somehow different than the way
XSLT uses a node-set? Or should I be able to access the children of a
node
in a node-set in a call to a Java extension?
Thanks for all your help!
-------------------------------------
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