cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mansour Al Akeel (JIRA)" <>
Subject [jira] [Commented] (COCOON3-125) Missing support for Catalog Resolver
Date Thu, 30 May 2013 12:10:20 GMT


Mansour Al Akeel commented on COCOON3-125:

The idea of having few dependencies is great, but I don't see this a fit in an optional component.
I can use  , there is access
restriction in the JDK on this class. 
I am not sure if  using reflection is an option. I can check if the CatalogResolver is in
the class path, and then load it. In this case, there is no need to include it in the pom,
but this is just a hack, and I don't see it a decent solution. 

If you think it is better to include this dependency in lower level pom, then this could be
a better solution. 

> Missing support for Catalog Resolver
> ------------------------------------
>                 Key: COCOON3-125
>                 URL:
>             Project: Cocoon 3
>          Issue Type: Improvement
>          Components: cocoon-sax
>    Affects Versions: 3.0.0-beta-1
>            Reporter: Mansour Al Akeel
>            Priority: Minor
>             Fix For: 3.0.0-beta-1
>         Attachments: CatalogResolver-support.diff
> When we load xml document using org.apache.cocoon.sax.util.XMLUtils.toSax, and the XML
document has a link to a DTD, the parser fails if the DTD is not in the specified location.
To solve this issue, a can be used. The same thing if we are using
document() function from an xslt and loaded document has a DTD. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message