Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.1.10, 2.1.11
-
None
-
None
-
Normal
Description
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.
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.