Hi Luca.
Thank you so much for help.
Here are all my components:
1. the pipeline:
<map:match pattern="*.html">
<map:generate src="{1}.html" type="html"/>
<map:transform src="test.xsl"/>
<map:serialize type="xml"/>
</map:match>
2. the imput file (test.html):
<html>
<head>
<title>Untitled</title>
</head>
<body>
<p>some text</p>
</body>
</html>
3. the xsl (test.xsl):
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform";
xmlns:fo="http://www.w3.org/1999/XSL/Format";
xmlns:saxon="http://icl.com/saxon";
extension-element-prefixes="saxon">
<xsl:template match="/">
<xsl:element name="root">
<xsl:text>HELLO </xsl:text>
<xsl:for-each select="//p">
<xsl:text>P content = </xsl:text>
<xsl:value-of select="."/>
</xsl:for-each>
</xsl:element>
</xsl:template>
</xsl:stylesheet>
As you can see, with such xml and xsl I should have one match for p element
and it's content should be output inside the root element. But it just
doesn't happen, it doesn't match the node. And now the interesting part
strats:
If I replace the select attribute of xsl:for-each to be
"descendant::node()[name()='p']"
instead of just "//p" (those two expressions mean exactly the same in the
XPath),
I suddenly get the match and the right answer from Cocoon.
Also, if I run this stylesheet externally of Cocoon (for example, using
XMLSpy XSLTransformation tool) I get the right answer for match "//p".
So I know that my stylesheet is OK, but I can't understand why it doesn't
work from Cocoon.
If somebody can explain this thing for me, I would be more than happy,
because I can't use the descendant::... style instead the // style in my
real (big) stylesheet.
Thank you all very much.
Hope somebody can help me with this.
Regards,
Anna
----- Original Message -----
From: "Luca Morandini" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, December 18, 2002 11:24 PM
Subject: RE: XPath problem in Cocoon?
Anna,
ok, let's try to sort it out, send us:
- The pipeline
- The XML to be transformed
- The XSLT
Possibly, strip off all the unnecessary stuff.
Best regards,
---------------------------------------------
Luca Morandini
GIS Consultant
[EMAIL PROTECTED]
http://utenti.tripod.it/lmorandini/index.html
---------------------------------------------
> -----Original Message-----
> From: Anna Afonchenko [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, December 18, 2002 3:25 PM
> To: [EMAIL PROTECTED]
> Subject: Re: XPath problem in Cocoon?
>
>
> Hi Konstantin.
> I know that my stylesheet works without Cocoon, I ran it through the batch
> file, using saxon. Even if I just run it using XSL Transformation of
XMLSpy,
> it works fine, and chooses the //p tags as it should.
> So I am sure the problem is with Cocoon, but I don't understand, if it's
my
> problem giving cocoon some wrong parameters (I don't know how this could
> happen) or maybe it is Cocoon problem? Using //node-name is a common XPath
> expression, it should work.
>
> Maybe somebody knows what's wrong?
> Does nobody having problems with matching this kind of XPath expression in
> Cocoon?
> It is very important for me, so if somebody can give me a hint of where
the
> problem lies, I would really appreciate this.
>
> Thank you very much for helping
>
> Anna
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
