You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Ralph Goers (JIRA)" <ji...@apache.org> on 2008/12/27 03:23:44 UTC
[jira] Created: (CONFIGURATION-355) Provide support for using the
XML Commons CatalogResolver or other EntityResolvers
Provide support for using the XML Commons CatalogResolver or other EntityResolvers
----------------------------------------------------------------------------------
Key: CONFIGURATION-355
URL: https://issues.apache.org/jira/browse/CONFIGURATION-355
Project: Commons Configuration
Issue Type: Improvement
Affects Versions: 1.6
Reporter: Ralph Goers
Fix For: 1.7
XMLConfiguration currently only supports a fairly primitive EntityResolver. Replacing this resolver requires creating a new DocumentBuilder, adding the EntityResolver to it and then updating XMLConfiguration to use it. This is fairly complicated and is difficult to do when using DefaultConfigurationBuilder.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (CONFIGURATION-355) Provide support for using the
XML Commons CatalogResolver or other EntityResolvers
Posted by "Ralph Goers (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CONFIGURATION-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralph Goers closed CONFIGURATION-355.
-------------------------------------
Resolution: Fixed
The code has been committed.
> Provide support for using the XML Commons CatalogResolver or other EntityResolvers
> ----------------------------------------------------------------------------------
>
> Key: CONFIGURATION-355
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-355
> Project: Commons Configuration
> Issue Type: Improvement
> Affects Versions: 1.6
> Reporter: Ralph Goers
> Fix For: 1.7
>
>
> XMLConfiguration currently only supports a fairly primitive EntityResolver. Replacing this resolver requires creating a new DocumentBuilder, adding the EntityResolver to it and then updating XMLConfiguration to use it. This is fairly complicated and is difficult to do when using DefaultConfigurationBuilder.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CONFIGURATION-355) Provide support for using the
XML Commons CatalogResolver or other EntityResolvers
Posted by "Ralph Goers (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CONFIGURATION-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659303#action_12659303 ]
Ralph Goers commented on CONFIGURATION-355:
-------------------------------------------
XMLConfiguration has been modified to allow a custom EntityResolver to be used with XMLConfiguration's DocumentBuilder. A CatalogResolver that can be configured into DefaultConfigurationBuilder's configuration has been created. DefaultConfigurationBuilder now allows a default EntityResolver to be configured.
> Provide support for using the XML Commons CatalogResolver or other EntityResolvers
> ----------------------------------------------------------------------------------
>
> Key: CONFIGURATION-355
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-355
> Project: Commons Configuration
> Issue Type: Improvement
> Affects Versions: 1.6
> Reporter: Ralph Goers
> Fix For: 1.7
>
>
> XMLConfiguration currently only supports a fairly primitive EntityResolver. Replacing this resolver requires creating a new DocumentBuilder, adding the EntityResolver to it and then updating XMLConfiguration to use it. This is fairly complicated and is difficult to do when using DefaultConfigurationBuilder.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.