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: Wed, 12 Jul 2000 11:15:20 -0400
- Organization: Blueprint Technologies, Inc.
- References: <200007120801.EAA20385@mulberrytech.com>
- Reply-To: xsl-list at mulberrytech dot com
> > 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.
> >
> [Kay Michael] Well as I say, it depends on the implementation. If
> you need help to do it in Saxon, I can show you how.
I was actually using a DOM parser. I would obtain one of the nodes in
the
node-set and call getChildNodes() on it and never get its children back.
Shouldn't it be as simple as that?
Now if I read in the entire XML file into a Java method and got that
node
as a result-tree fragment, I could get to the children but not as a
node-set.
--
-------------------------------------
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