On 02.12.2003 11:24, Carmona Perez, David wrote:

It occurs with a standard new seeded project, with no modifications apart from copying 
Saxon.jar in WEB-INF/lib
By the way, this behaviour only happens with Forrest 0.6.5, but not with Cocoon 2.1.2 
or 2.1.3.  It must be some Cocoon.xconf issue in Forrest distribution.

This makes it really weird. Can you compare the parts related to Saxon?


The following entry is commented out:

  <!--+
      | Saxon XSLT Processor
      | For old (6.5.2) Saxon use:
      |  <parameter name="transformer-factory" 
value="com.icl.saxon.TransformerFactoryImpl"/>
      | For new (7.x?) Saxon use:
      |  <parameter name="transformer-factory" 
value="net.sf.saxon.TransformerFactoryImpl"/>
  <component logger="core.xslt-processor"
             role="org.apache.excalibur.xml.xslt.XSLTProcessor/saxon"
             class="org.apache.excalibur.xml.xslt.XSLTProcessorImpl">
     <parameter name="use-store" value="false"/>
     <parameter name="transformer-factory" 
value="com.icl.saxon.TransformerFactoryImpl"/>
  </component>
  +-->

I know that you have to include the above code (i.e. without comments) and add an entry in the sitemap matching the role. AFAIK Vadim always uses Saxon with Cocoon.


Joerg

-----Mensaje original-----
De: Joerg Heinicke [mailto:[EMAIL PROTECTED]

On 01.12.2003 10:56, Carmona Perez, David wrote:


Hi all,

Does anyone know why I receive a NullPointerException when I place saxon-6.5.3.jar in 
the WEB-INF/lib file
in an installation of Cocoon 2.1.2 that used to run ok?

I used the Cocoon bundled with the latest version of Forrest.

Are there any conflicts with Xalan?

Thanks in advance for any help.

Here is a detailed log:


Do you have configured something in the cocoon.xconf (search for 'Saxon'
there)? And in the map:components section of the sitemap?

Joerg


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to