This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: XPath weirdness!!
- To: xsl-list at lists dot mulberrytech dot com
- Subject: RE: [xsl] XPath weirdness!!
- From: "Clapham, Paul" <pclapham at core-mark dot com>
- Date: Wed, 25 Jul 2001 11:39:56 -0700
- Reply-To: xsl-list at lists dot mulberrytech dot com
As I recall, the error was about your XML document and not about your XSL,
wasn't it? Show us the document.
PC2
-----Original Message-----
From: Kris Kolodziej [mailto:kkolodziej@syncline.com]
Sent: July 25, 2001 10:14
To: xsl-list@lists.mulberrytech.com
Subject: [xsl] XPath weirdness!!
This is related to my previous problem with the "&x#3c." So I figured
out that I was doing something wrong with the XPath locations...However,
now I am experiencing some weird things with XPath. Take the following
example for instance:
This works but it only give me the "x" value (and I sure do want to get
both x AND y).
Notice that for "y" I only have "/@y". This is because when I do the
same thing as I did for "x" (meaning writing "<xsl:value-of
select="//@y"/>" ) I get the "&x#3c" error!!! WHY??!
<xsl:when test="//SpatialQuery/Buffer">
<MULTIPOINT>
<xsl:for-each select="//Point">
<POINT>
<xsl:attribute name="x">
<xsl:value-of select="//@x"/>
</xsl:attribute>
<xsl:attribute name="y">
<xsl:value-of select="/@y"/>
</xsl:attribute>
</POINT>
</xsl:for-each>
</MULTIPOINT>
It also works when I do the vice versa of what I have ("/@x" and "//@y")
but I can't have it written the same way.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list