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] Closed: (COCOON-2164) Bug in JaxpResolver in validation block
Date Fri, 01 Feb 2008 18:15:08 GMT

     [ https://issues.apache.org/jira/browse/COCOON-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Carsten Ziegeler closed COCOON-2164.
------------------------------------

    Resolution: Fixed

> Bug in JaxpResolver in validation block
> ---------------------------------------
>
>                 Key: COCOON-2164
>                 URL: https://issues.apache.org/jira/browse/COCOON-2164
>             Project: Cocoon
>          Issue Type: Bug
>          Components: Blocks: Validation
>    Affects Versions: 2.1.10, 2.1.11
>            Reporter: Nico Verwer
>            Assignee: Carsten Ziegeler
>
> There is a bug in the validation block, in org.apache.cocoon.components.validation.jaxp.JaxpResolver.
> It implements org.w3c.dom.ls.LSResourceResolver, but the parameter order in method resolveResource
is wrong.
> According to the API of org.w3c.dom.ls.LSResourceResolver, this should be:
> resolveResource(String type, String namespaceURI, String publicId, String systemId, String
baseURI)
> but in org.apache.cocoon.components.validation.jaxp.JaxpResolver it is
> resolveResource(String type, String namespace, String systemId, String publicId, String
base)
> The publicId and systemId have been swapped. This prevents the validation block from
using XML schemas that have import or include.
> Using the parameters in the right order solves this problem.

-- 
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