You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Kristoff Kiefer (JIRA)" <ji...@apache.org> on 2007/08/08 15:06:59 UTC
[jira] Created: (CONFIGURATION-290) Ability to register() Entity
URLs for Public IDs like in Digester
Ability to register() Entity URLs for Public IDs like in Digester
-----------------------------------------------------------------
Key: CONFIGURATION-290
URL: https://issues.apache.org/jira/browse/CONFIGURATION-290
Project: Commons Configuration
Issue Type: New Feature
Affects Versions: 1.4
Environment: Configuration 1.4
Reporter: Kristoff Kiefer
When trying to parse a XMLConfiguration from behind a firewall. Configuration will quit due to a refused connection when trying to resolve a Public ID to an external entity. (web.xml DTD in this case)
With Digester I'd know what to to, simply register() a local copy of the file in question)
It would be nice to do the same for Configuration wouldn't it?
(It would save me from writing my own EntityResolver)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CONFIGURATION-290) Ability to register() Entity
URLs for Public IDs like in Digester
Posted by "Oliver Heger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CONFIGURATION-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oliver Heger resolved CONFIGURATION-290.
----------------------------------------
Resolution: Fixed
A new method registerEntityId() was added to XMLConfiguration for this purpose. DefaultConfigurationBuilder was also extended so that entities registered for the builder will be passed to the loaded XMLConfigurations.
> Ability to register() Entity URLs for Public IDs like in Digester
> -----------------------------------------------------------------
>
> Key: CONFIGURATION-290
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-290
> Project: Commons Configuration
> Issue Type: New Feature
> Affects Versions: 1.4
> Environment: Configuration 1.4
> Reporter: Kristoff Kiefer
> Assignee: Oliver Heger
> Fix For: 1.5
>
>
> When trying to parse a XMLConfiguration from behind a firewall. Configuration will quit due to a refused connection when trying to resolve a Public ID to an external entity. (web.xml DTD in this case)
> With Digester I'd know what to to, simply register() a local copy of the file in question)
> It would be nice to do the same for Configuration wouldn't it?
> (It would save me from writing my own EntityResolver)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CONFIGURATION-290) Ability to register() Entity
URLs for Public IDs like in Digester
Posted by "Oliver Heger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CONFIGURATION-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oliver Heger updated CONFIGURATION-290:
---------------------------------------
Fix Version/s: 1.5
Sounds reasonable.
It would also be nice if DefaultConfigurationBuilder supported a similar registration mechanism that is used by the loaded child configurations. However this will be probably more difficult to implement.
> Ability to register() Entity URLs for Public IDs like in Digester
> -----------------------------------------------------------------
>
> Key: CONFIGURATION-290
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-290
> Project: Commons Configuration
> Issue Type: New Feature
> Affects Versions: 1.4
> Environment: Configuration 1.4
> Reporter: Kristoff Kiefer
> Fix For: 1.5
>
>
> When trying to parse a XMLConfiguration from behind a firewall. Configuration will quit due to a refused connection when trying to resolve a Public ID to an external entity. (web.xml DTD in this case)
> With Digester I'd know what to to, simply register() a local copy of the file in question)
> It would be nice to do the same for Configuration wouldn't it?
> (It would save me from writing my own EntityResolver)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.