You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Michiel Kalkman (JIRA)" <ji...@apache.org> on 2006/06/12 14:07:32 UTC
[jira] Created: (CONFIGURATION-215) Using relative URLs
Using relative URLs
-------------------
Key: CONFIGURATION-215
URL: http://issues.apache.org/jira/browse/CONFIGURATION-215
Project: Commons Configuration
Type: Improvement
Reporter: Michiel Kalkman
It would be useful to be able to specify URLs in configuration item values that are relative to the configuration.
A sample. I have the following files.
A/config.xml which refers to
B/specificConfigForB.xml which refers to
B/somefile
Now specifying the location of somefile in specificConfigForB.xml should be possible using a relative URL, such that it is possible to retrieve the absolute URL of somefile through:
a) the absolute URL of A/config.xml (e.g.: file:/c:/A/config.xml or http://A/config.xml)
b) the relative URL of somefile specified in B/specificConfigForB.xml (like <somefile>somefile</somefile>)
(1) One solution is to make it possible to find the location of the configuration file that specifies the relative URL. Or more general, commons config should know where a given configuration item is stored.
In this case it might be an idea to implement a getURL() on the Configuration interface which uses:
1. the absolute URL of the composite configuration file, (A/config.xml)
2. the relative URL to the specfying configuration file, (B/specificConfigForB.xml)
3. the relative URL specified (in B/specificConfigForB.xml)
(2) Another solution is to specify a special meta variable (like ${url}) that can be used to specify the location of the specifying configuration file wrt the composite configuration file. E.g. <somefile>${url}/somefile</somefile> would result in ../B/somefile.
(3) Another solution would be to specify a special attribute to indicate that the value specified is an URL. Like <somefile type="URL">somefile</somefile>.
The advantage of solution (1) is that no extra semantics are introduced to the configuration files. Furthermore, it might possibly be useful in debugging situations. The advantages of solution (2) is that in this manner other meta variables might be introduced. The disadvantage of solution (3) is that this one cannot be applied to property files.
See also http://mail-archives.apache.org/mod_mbox/jakarta-commons-user/200606.mbox/%3c448AE9A8.2030003@oliver-heger.de%3e
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[jira] Commented: (CONFIGURATION-215) Using relative URLs
Posted by "Oliver Heger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CONFIGURATION-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463705 ]
Oliver Heger commented on CONFIGURATION-215:
--------------------------------------------
I never got a response to my last suggestions. What is the current status of this issue? Is this feature still needed?
> Using relative URLs
> -------------------
>
> Key: CONFIGURATION-215
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-215
> Project: Commons Configuration
> Issue Type: Improvement
> Reporter: Michiel Kalkman
> Priority: Minor
>
> It would be useful to be able to specify URLs in configuration item values that are relative to the configuration.
> A sample. I have the following files.
> A/config.xml which refers to
> B/specificConfigForB.xml which refers to
> B/somefile
> Now specifying the location of somefile in specificConfigForB.xml should be possible using a relative URL, such that it is possible to retrieve the absolute URL of somefile through:
> a) the absolute URL of A/config.xml (e.g.: file:/c:/A/config.xml or http://A/config.xml)
> b) the relative URL of somefile specified in B/specificConfigForB.xml (like <somefile>somefile</somefile>)
> (1) One solution is to make it possible to find the location of the configuration file that specifies the relative URL. Or more general, commons config should know where a given configuration item is stored.
> In this case it might be an idea to implement a getURL() on the Configuration interface which uses:
> 1. the absolute URL of the composite configuration file, (A/config.xml)
> 2. the relative URL to the specfying configuration file, (B/specificConfigForB.xml)
> 3. the relative URL specified (in B/specificConfigForB.xml)
> (2) Another solution is to specify a special meta variable (like ${url}) that can be used to specify the location of the specifying configuration file wrt the composite configuration file. E.g. <somefile>${url}/somefile</somefile> would result in ../B/somefile.
> (3) Another solution would be to specify a special attribute to indicate that the value specified is an URL. Like <somefile type="URL">somefile</somefile>.
> The advantage of solution (1) is that no extra semantics are introduced to the configuration files. Furthermore, it might possibly be useful in debugging situations. The advantages of solution (2) is that in this manner other meta variables might be introduced. The disadvantage of solution (3) is that this one cannot be applied to property files.
> See also http://mail-archives.apache.org/mod_mbox/jakarta-commons-user/200606.mbox/%3c448AE9A8.2030003@oliver-heger.de%3e
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[jira] Updated: (CONFIGURATION-215) Using relative URLs
Posted by "Oliver Heger (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/CONFIGURATION-215?page=all ]
Oliver Heger updated CONFIGURATION-215:
---------------------------------------
Priority: Minor (was: Major)
Solution (1) would be hard to implement for some of the composite configuration classes. I am not sure whether this effort is worth the value it gains because finding out from which configuration source a certain property was loaded does not seem to me to be such a typical use case - but I may be wrong.
Solution (3) is too specific for my taste.
Solution (2) would be my favorite because of the additional flexibility it provides. For this request that would mean introducing a predefined variable called ${config_url} or whatever that is replaced by the URL from which the configuration file was loaded. However for composite configurations there is still the problem how this variable should be resolved. This would require knowledge from which source the property was loaded (same as (1)) and also extending the variable substitution algorithm to take the property, in which the variable is placed, into account.
Could you live with the following simpler approach: Configurations stored in a composite configuration can be accessed either by a numeric index or (in the case of CombinedConfiguration) by a name. So a composite configuration could provide a family of meta variables of the form ${config_url.0}, ${config_url.1}, or ${config_url_name}, which will be replaced by the URL of the corresponding configuration source. Then it is in the responsibility of the developer to choose the correct variable.
> Using relative URLs
> -------------------
>
> Key: CONFIGURATION-215
> URL: http://issues.apache.org/jira/browse/CONFIGURATION-215
> Project: Commons Configuration
> Type: Improvement
> Reporter: Michiel Kalkman
> Priority: Minor
>
> It would be useful to be able to specify URLs in configuration item values that are relative to the configuration.
> A sample. I have the following files.
> A/config.xml which refers to
> B/specificConfigForB.xml which refers to
> B/somefile
> Now specifying the location of somefile in specificConfigForB.xml should be possible using a relative URL, such that it is possible to retrieve the absolute URL of somefile through:
> a) the absolute URL of A/config.xml (e.g.: file:/c:/A/config.xml or http://A/config.xml)
> b) the relative URL of somefile specified in B/specificConfigForB.xml (like <somefile>somefile</somefile>)
> (1) One solution is to make it possible to find the location of the configuration file that specifies the relative URL. Or more general, commons config should know where a given configuration item is stored.
> In this case it might be an idea to implement a getURL() on the Configuration interface which uses:
> 1. the absolute URL of the composite configuration file, (A/config.xml)
> 2. the relative URL to the specfying configuration file, (B/specificConfigForB.xml)
> 3. the relative URL specified (in B/specificConfigForB.xml)
> (2) Another solution is to specify a special meta variable (like ${url}) that can be used to specify the location of the specifying configuration file wrt the composite configuration file. E.g. <somefile>${url}/somefile</somefile> would result in ../B/somefile.
> (3) Another solution would be to specify a special attribute to indicate that the value specified is an URL. Like <somefile type="URL">somefile</somefile>.
> The advantage of solution (1) is that no extra semantics are introduced to the configuration files. Furthermore, it might possibly be useful in debugging situations. The advantages of solution (2) is that in this manner other meta variables might be introduced. The disadvantage of solution (3) is that this one cannot be applied to property files.
> See also http://mail-archives.apache.org/mod_mbox/jakarta-commons-user/200606.mbox/%3c448AE9A8.2030003@oliver-heger.de%3e
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[jira] Commented: (CONFIGURATION-215) Using relative URLs
Posted by "Oliver Heger (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/CONFIGURATION-215?page=comments#action_12416623 ]
Oliver Heger commented on CONFIGURATION-215:
--------------------------------------------
Two thoughts:
- Such a method for checking from which source a property was loaded would only make sense for composite configurations, i.e. ATM the classes CompositeConfiguration and CombinedConfiguration, wouldn't it? For other - simple - configurations the source is always the configuration itself.
- getURL() would only be a special case that is applicable to file-based configurations. Maybe somewhen later somebody dealing with different database configurations might want to find out, from which database table a certain property was loaded. Then a URL would be useless. The same is true for JNDI configurations you mentioned already.
So I would suggest the following solution: A method
Configuration getSource(String key);
can be added to composite configurations, which retrieves the source configuration of a specified property.
For your special use case, when you know that you are dealing with file-based configurations only, you can then do something like:
URL url = ((FileConfiguration) compositeConfiguration.getSource("myProperty")).getURL();
Would this be okay with you?
> Using relative URLs
> -------------------
>
> Key: CONFIGURATION-215
> URL: http://issues.apache.org/jira/browse/CONFIGURATION-215
> Project: Commons Configuration
> Type: Improvement
> Reporter: Michiel Kalkman
> Priority: Minor
>
> It would be useful to be able to specify URLs in configuration item values that are relative to the configuration.
> A sample. I have the following files.
> A/config.xml which refers to
> B/specificConfigForB.xml which refers to
> B/somefile
> Now specifying the location of somefile in specificConfigForB.xml should be possible using a relative URL, such that it is possible to retrieve the absolute URL of somefile through:
> a) the absolute URL of A/config.xml (e.g.: file:/c:/A/config.xml or http://A/config.xml)
> b) the relative URL of somefile specified in B/specificConfigForB.xml (like <somefile>somefile</somefile>)
> (1) One solution is to make it possible to find the location of the configuration file that specifies the relative URL. Or more general, commons config should know where a given configuration item is stored.
> In this case it might be an idea to implement a getURL() on the Configuration interface which uses:
> 1. the absolute URL of the composite configuration file, (A/config.xml)
> 2. the relative URL to the specfying configuration file, (B/specificConfigForB.xml)
> 3. the relative URL specified (in B/specificConfigForB.xml)
> (2) Another solution is to specify a special meta variable (like ${url}) that can be used to specify the location of the specifying configuration file wrt the composite configuration file. E.g. <somefile>${url}/somefile</somefile> would result in ../B/somefile.
> (3) Another solution would be to specify a special attribute to indicate that the value specified is an URL. Like <somefile type="URL">somefile</somefile>.
> The advantage of solution (1) is that no extra semantics are introduced to the configuration files. Furthermore, it might possibly be useful in debugging situations. The advantages of solution (2) is that in this manner other meta variables might be introduced. The disadvantage of solution (3) is that this one cannot be applied to property files.
> See also http://mail-archives.apache.org/mod_mbox/jakarta-commons-user/200606.mbox/%3c448AE9A8.2030003@oliver-heger.de%3e
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[jira] Commented: (CONFIGURATION-215) Using relative URLs
Posted by "Michiel Kalkman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CONFIGURATION-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464489 ]
Michiel Kalkman commented on CONFIGURATION-215:
-----------------------------------------------
My apologies for not reacting sooner. This item did get less relevant for me and it "escaped" from my todo list somehow.
However, I think the item could pop up again in the (near) future, so the item might get relevant for me again.
The solution you suggest definitely seems okay to me - it would resolve the original issue I had.
> Using relative URLs
> -------------------
>
> Key: CONFIGURATION-215
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-215
> Project: Commons Configuration
> Issue Type: Improvement
> Reporter: Michiel Kalkman
> Priority: Minor
>
> It would be useful to be able to specify URLs in configuration item values that are relative to the configuration.
> A sample. I have the following files.
> A/config.xml which refers to
> B/specificConfigForB.xml which refers to
> B/somefile
> Now specifying the location of somefile in specificConfigForB.xml should be possible using a relative URL, such that it is possible to retrieve the absolute URL of somefile through:
> a) the absolute URL of A/config.xml (e.g.: file:/c:/A/config.xml or http://A/config.xml)
> b) the relative URL of somefile specified in B/specificConfigForB.xml (like <somefile>somefile</somefile>)
> (1) One solution is to make it possible to find the location of the configuration file that specifies the relative URL. Or more general, commons config should know where a given configuration item is stored.
> In this case it might be an idea to implement a getURL() on the Configuration interface which uses:
> 1. the absolute URL of the composite configuration file, (A/config.xml)
> 2. the relative URL to the specfying configuration file, (B/specificConfigForB.xml)
> 3. the relative URL specified (in B/specificConfigForB.xml)
> (2) Another solution is to specify a special meta variable (like ${url}) that can be used to specify the location of the specifying configuration file wrt the composite configuration file. E.g. <somefile>${url}/somefile</somefile> would result in ../B/somefile.
> (3) Another solution would be to specify a special attribute to indicate that the value specified is an URL. Like <somefile type="URL">somefile</somefile>.
> The advantage of solution (1) is that no extra semantics are introduced to the configuration files. Furthermore, it might possibly be useful in debugging situations. The advantages of solution (2) is that in this manner other meta variables might be introduced. The disadvantage of solution (3) is that this one cannot be applied to property files.
> See also http://mail-archives.apache.org/mod_mbox/jakarta-commons-user/200606.mbox/%3c448AE9A8.2030003@oliver-heger.de%3e
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[jira] Resolved: (CONFIGURATION-215) Using relative URLs
Posted by "Oliver Heger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CONFIGURATION-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oliver Heger resolved CONFIGURATION-215.
----------------------------------------
Resolution: Fixed
getSource() methods were added to CompositeConfiguration and CombinedConfiguration. Please have a look at the Javadocs for an exact description of the semantics.
> Using relative URLs
> -------------------
>
> Key: CONFIGURATION-215
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-215
> Project: Commons Configuration
> Issue Type: Improvement
> Affects Versions: 1.3
> Reporter: Michiel Kalkman
> Assigned To: Oliver Heger
> Priority: Minor
> Fix For: 1.5
>
>
> It would be useful to be able to specify URLs in configuration item values that are relative to the configuration.
> A sample. I have the following files.
> A/config.xml which refers to
> B/specificConfigForB.xml which refers to
> B/somefile
> Now specifying the location of somefile in specificConfigForB.xml should be possible using a relative URL, such that it is possible to retrieve the absolute URL of somefile through:
> a) the absolute URL of A/config.xml (e.g.: file:/c:/A/config.xml or http://A/config.xml)
> b) the relative URL of somefile specified in B/specificConfigForB.xml (like <somefile>somefile</somefile>)
> (1) One solution is to make it possible to find the location of the configuration file that specifies the relative URL. Or more general, commons config should know where a given configuration item is stored.
> In this case it might be an idea to implement a getURL() on the Configuration interface which uses:
> 1. the absolute URL of the composite configuration file, (A/config.xml)
> 2. the relative URL to the specfying configuration file, (B/specificConfigForB.xml)
> 3. the relative URL specified (in B/specificConfigForB.xml)
> (2) Another solution is to specify a special meta variable (like ${url}) that can be used to specify the location of the specifying configuration file wrt the composite configuration file. E.g. <somefile>${url}/somefile</somefile> would result in ../B/somefile.
> (3) Another solution would be to specify a special attribute to indicate that the value specified is an URL. Like <somefile type="URL">somefile</somefile>.
> The advantage of solution (1) is that no extra semantics are introduced to the configuration files. Furthermore, it might possibly be useful in debugging situations. The advantages of solution (2) is that in this manner other meta variables might be introduced. The disadvantage of solution (3) is that this one cannot be applied to property files.
> See also http://mail-archives.apache.org/mod_mbox/jakarta-commons-user/200606.mbox/%3c448AE9A8.2030003@oliver-heger.de%3e
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[jira] Commented: (CONFIGURATION-215) Using relative URLs
Posted by "Michiel Kalkman (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/CONFIGURATION-215?page=comments#action_12416477 ]
Michiel Kalkman commented on CONFIGURATION-215:
-----------------------------------------------
Knowing in which location a certain configuration item was specificied, would help in implementing a getURL() method on the configuration interface. Maybe it would also be useful for debugging purposes, e.g. when a configuration item is specified in multiple locations, it could be used to determine which one was chosen.
I think it's important to keep the configuration files as simple and intuitive as possible in order to make usage and specification of configurations as easy. In particular, you don't want a programmer to know how the configuration is structured; except for the location of the root configuration, and the names / types of the configuration items, he should know nothing more.
So, option 1 is still my favorite solution. Maybe that for some options this can not be implemented (JNDI comes to mind - but I never used that in combination with commons configuration).
> Using relative URLs
> -------------------
>
> Key: CONFIGURATION-215
> URL: http://issues.apache.org/jira/browse/CONFIGURATION-215
> Project: Commons Configuration
> Type: Improvement
> Reporter: Michiel Kalkman
> Priority: Minor
>
> It would be useful to be able to specify URLs in configuration item values that are relative to the configuration.
> A sample. I have the following files.
> A/config.xml which refers to
> B/specificConfigForB.xml which refers to
> B/somefile
> Now specifying the location of somefile in specificConfigForB.xml should be possible using a relative URL, such that it is possible to retrieve the absolute URL of somefile through:
> a) the absolute URL of A/config.xml (e.g.: file:/c:/A/config.xml or http://A/config.xml)
> b) the relative URL of somefile specified in B/specificConfigForB.xml (like <somefile>somefile</somefile>)
> (1) One solution is to make it possible to find the location of the configuration file that specifies the relative URL. Or more general, commons config should know where a given configuration item is stored.
> In this case it might be an idea to implement a getURL() on the Configuration interface which uses:
> 1. the absolute URL of the composite configuration file, (A/config.xml)
> 2. the relative URL to the specfying configuration file, (B/specificConfigForB.xml)
> 3. the relative URL specified (in B/specificConfigForB.xml)
> (2) Another solution is to specify a special meta variable (like ${url}) that can be used to specify the location of the specifying configuration file wrt the composite configuration file. E.g. <somefile>${url}/somefile</somefile> would result in ../B/somefile.
> (3) Another solution would be to specify a special attribute to indicate that the value specified is an URL. Like <somefile type="URL">somefile</somefile>.
> The advantage of solution (1) is that no extra semantics are introduced to the configuration files. Furthermore, it might possibly be useful in debugging situations. The advantages of solution (2) is that in this manner other meta variables might be introduced. The disadvantage of solution (3) is that this one cannot be applied to property files.
> See also http://mail-archives.apache.org/mod_mbox/jakarta-commons-user/200606.mbox/%3c448AE9A8.2030003@oliver-heger.de%3e
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[jira] Updated: (CONFIGURATION-215) Using relative URLs
Posted by "Oliver Heger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CONFIGURATION-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oliver Heger updated CONFIGURATION-215:
---------------------------------------
Fix Version/s: 1.5
Affects Version/s: 1.3 Final
Setting fix version to release 1.5, assuming that 1.4 can come out soon. A solution of this problem would also be helpful for the requested feature of saving back changes made at a composite configuration.
> Using relative URLs
> -------------------
>
> Key: CONFIGURATION-215
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-215
> Project: Commons Configuration
> Issue Type: Improvement
> Affects Versions: 1.3 Final
> Reporter: Michiel Kalkman
> Priority: Minor
> Fix For: 1.5
>
>
> It would be useful to be able to specify URLs in configuration item values that are relative to the configuration.
> A sample. I have the following files.
> A/config.xml which refers to
> B/specificConfigForB.xml which refers to
> B/somefile
> Now specifying the location of somefile in specificConfigForB.xml should be possible using a relative URL, such that it is possible to retrieve the absolute URL of somefile through:
> a) the absolute URL of A/config.xml (e.g.: file:/c:/A/config.xml or http://A/config.xml)
> b) the relative URL of somefile specified in B/specificConfigForB.xml (like <somefile>somefile</somefile>)
> (1) One solution is to make it possible to find the location of the configuration file that specifies the relative URL. Or more general, commons config should know where a given configuration item is stored.
> In this case it might be an idea to implement a getURL() on the Configuration interface which uses:
> 1. the absolute URL of the composite configuration file, (A/config.xml)
> 2. the relative URL to the specfying configuration file, (B/specificConfigForB.xml)
> 3. the relative URL specified (in B/specificConfigForB.xml)
> (2) Another solution is to specify a special meta variable (like ${url}) that can be used to specify the location of the specifying configuration file wrt the composite configuration file. E.g. <somefile>${url}/somefile</somefile> would result in ../B/somefile.
> (3) Another solution would be to specify a special attribute to indicate that the value specified is an URL. Like <somefile type="URL">somefile</somefile>.
> The advantage of solution (1) is that no extra semantics are introduced to the configuration files. Furthermore, it might possibly be useful in debugging situations. The advantages of solution (2) is that in this manner other meta variables might be introduced. The disadvantage of solution (3) is that this one cannot be applied to property files.
> See also http://mail-archives.apache.org/mod_mbox/jakarta-commons-user/200606.mbox/%3c448AE9A8.2030003@oliver-heger.de%3e
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org