Dave Smith wrote:
> 
> When deploying the cocoon.war file I get the following error ...

This is due to an incorrectly versioned JAXP parser (you want JAXP 1.1
compliance).  You have two alternatives: get Jetty to use Xerces, or
get Cocoon to use Xerces.

There are instructions in the cocoon.xconf file to use Xerces directly.

> 
> Could not configure Cocoon environment
> 
> org.xml.sax.SAXNotSupportedException: Property:
> http://xml.org/sax/properties/lexical-handler
> +       at
> org.apache.crimson.parser.XMLReaderImpl.setProperty(XMLReaderImpl.java:248)
> +       at
> org.apache.cocoon.components.parser.JaxpParser.parse(JaxpParser.java:67)
> +       at org.apache.cocoon.Cocoon.configure(Cocoon.java:216)
> +       at org.apache.cocoon.Cocoon.initialize(Cocoon.java:160)
> +       at
> org.apache.cocoon.servlet.CocoonServlet.createCocoon(CocoonServlet.java:634)
> +       at
> org.apache.cocoon.servlet.CocoonServlet.init(CocoonServlet.java:164)
> +       at
> com.mortbay.Jetty.Servlet.ServletHolder.getServlet(ServletHolder.java:306)
> +       at
> com.mortbay.Jetty.Servlet.ServletHolder.initialize(ServletHolder.java:194)
> +       at
> com.mortbay.Jetty.Servlet.ServletHandler.start(ServletHandler.java:185)
> +       at com.mortbay.HTTP.HandlerContext.start(HandlerContext.java:1053)
> +       at
> com.mortbay.Jetty.Servlet.WebApplicationContext.start(WebApplicationContext.java:330)
> +       at com.mortbay.HTTP.HttpServer.start(HttpServer.java:127)
> +       at com.mortbay.Jetty.Server.main(Server.java:226)
> 
> I checked the archives and there was a reference to a similar problem in
> the xalan parser but it was supposedly fixed in November of last year.
> 
> I am running jetty 3.1R6 on linux 2.2.18 with Blackdown JDK 1.3
> 
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
> 
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail: <[EMAIL PROTECTED]>

S/MIME Cryptographic Signature

Reply via email to