cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COCOON-136) Parser failure with validate=true when processing stylesheet
Date Tue, 13 Feb 2007 10:02:06 GMT

    [ https://issues.apache.org/jira/browse/COCOON-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472603
] 

Carsten Ziegeler commented on COCOON-136:
-----------------------------------------

I think we should add a validating and a non-validating parser and make the non-validating
the default, like Bruno suggested. Each component has to be checked if it should be made configurable
to use validation or use the non-validating resp. validating parser hard-coded.


> Parser failure with validate=true when processing stylesheet
> ------------------------------------------------------------
>
>                 Key: COCOON-136
>                 URL: https://issues.apache.org/jira/browse/COCOON-136
>             Project: Cocoon
>          Issue Type: Bug
>          Components: * Cocoon Core
>    Affects Versions: 2.0.5-dev (Current CVS)
>         Environment: Operating System: All
> Platform: All
>            Reporter: David Crossley
>         Assigned To: Cocoon Developers Team
>
> Problem
> -------
> Recently we were able to switch on validate=true during "build docs" to enable
> validation of Cocoon's own xdocs. That was working beautifully to detect any
> errors that may have crept into CVS.
>  
> Then a bug was fixed in XSLTProcessorImpl.java that had been disguising this
> current bug. The exceptions described below were suddenly thrown when trying to
> use the "validate=true" option.
>  
> It seems that Xerces is getting confused about the namespace declaration in the
> stylesheets.
>  
> Description
> -----------
> In mid-January, a bug was discovered and fixed in
> cocoon/components/xslt/XSLTProcessorImpl.java - Revision 1.5
> VG> I discovered that XSLTProcessorImpl code have some flaws,
> > like it is not using toSAX method of the Source interface, thus
> > requiring to serialize and then parse again XML (result: slower
> > processing of cocoon: protocol).
> We presume that a separate parser was being used by XSLTProcessorImpl.java
> and that parser did not have the "validate" parameter set. Now that the
> default parser is being used (which has "validate=true") the exceptions start
> to appear.
>  
> Some other relevant discussion
> ------------------------------
>  
> [VOTE] XML validation during build docs
> Date: Tue, 15 Jan 2002 16:36:22 +1100
> ... resounding YES, do switch it on ...
>  
> RE: build docs issue: XSL/Transform namespace changed
> Date: Wed, 23 Jan 2002 21:49:04 -0500
> Error listing
> -------------
> ERROR   10117   [        ] (): Logicsheet.getTransformerHandler: Exception
> org.apache.cocoon.ProcessingException:
> Error in creating Transform Handler: org.xml.sax.SAXParseException:
> General Schema Error: Grammar with uri: http://www.w3.org/1999/XSL/Transform
> , can not be found; schema namespace may be wrong:
> Xerces supports schemas from the "http://www.w3.org/2001/XMLSchema"
> namespace or the instance document's namespace may not match the
> targetNamespace of the schema.
> at
> org.apache.cocoon.components.xslt.XSLTProcessorImpl.getTransformerHandler(XSLTProcessorImpl.java:223)
> -------------

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message