Jeremy, I have got exactly the same problem when I use saxon 6.5.2 with
cocoon 2.0.3 or cocoon 2.1 (invalid processing instruction name
(saxon:warning) at line 13 column -1 (what column is that?)). I have
configured saxon role in the same way as you (as described in
http://outerthought.net/wiki/Wiki.jsp?page=DocbookTransformation) and I know
that the xslt stylesheet is correct because I have tested it with xalan.

Does anyone know how to solve this problem?

Oskar

----- Original Message -----
From: "Jeremy Quinn" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, November 16, 2002 3:26 PM
Subject: Weird Saxon errors


> I just switched to using Saxon 6.5.2 with Cocoon 2.1-dev as lots of
> people say it is faster than xalan and xsltc.
>
> I get lots of strange errors in my stylesheets, that I cannot work out.
> These are stylesheets that are largely trivial, and work fine in Xalan
> and XSLTC.
>
> Has anyone else noticed this kind of behaviour?
>
> Example:
>
> org.apache.cocoon.ProcessingException: Could not read resource
> file:/Users/jermq/Library/TomCat/webapps/cocoon/iniva/parts/components/
> meta-data.xml:
> file:/Users/jermq/Library/TomCat/webapps/cocoon/iniva/parts/xsl/macro-
> filter.xsl:12:-1:javax.xml.transform.TransformerException: Invalid
> processing instruction name (saxon:warning)
>
> this is line 12, column -1 (sic)
>
> <?xml version="1.0"?>
>
> <xsl:stylesheet version="1.0"
> xmlns:xsl="http://www.w3.org/1999/XSL/Transform";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns:saxon="http://icl.com/saxon";
> exclude-result-prefixes="saxon"
>  >
>
> <xsl:param name="idref"/>
>
> <xsl:template match="doc">
> <xsl:apply-templates select="macro[@id=$idref]/*"/>
> </xsl:template>
>
>    <xsl:template match="@*|node()"
> priority="-2"><xsl:copy><xsl:apply-templates
> select="@*|node()"/></xsl:copy></xsl:template>
>    <xsl:template match="text()" priority="-1"><xsl:value-of
> select="."/></xsl:template>
>
> </xsl:stylesheet>
>
> Where line 12 is:
>
> <xsl:template match="@*|node()"
> priority="-2"><xsl:copy><xsl:apply-templates
> select="@*|node()"/></xsl:copy></xsl:template>
>
> Do What???
> There is nothing wrong with this line according to the other XSLT
> engines.
> Invalid processing instruction??????
>
>
> This is my config:
>
> in cocoon.xconf:
>
>    <xslt-processor logger="core.xslt-processor">
>       <parameter name="use-store" value="false"/>
>       <parameter name="incremental-processing" value="true"/>
>    </xslt-processor>
>
>    <component
>      role="org.apache.cocoon.components.xslt.XSLTProcessor/Saxon"
>      class="org.apache.cocoon.components.xslt.XSLTProcessorImpl"
>      logger="core.xslt-processor">
>     <parameter name="use-store" value="true"/>
>     <parameter name="incremental-processing" value="false"/>
>     <parameter name="transformer-factory"
>      value="com.icl.saxon.TransformerFactoryImpl"/>
>    </component>
>
> in sitemap.xmap:
>
> <map:transformer logger="sitemap.transformer.saxon" name="saxon"
>    pool-grow="2" pool-max="32" pool-min="8"
>         src="org.apache.cocoon.transformation.TraxTransformer">
>   <use-request-parameters>false</use-request-parameters>
>   <use-browser-capabilities-db>false</use-browser-capabilities-db>
>   <xslt-processor-role>
>          org.apache.cocoon.components.xslt.XSLTProcessor/Saxon
>        </xslt-processor-role>
> </map:transformer>
>
>
> Any suggestions would be gratefully accepted.
>
> regards Jeremy
>
>
> ---------------------------------------------------------------------
> 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]>

Reply via email to