You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by bu...@apache.org on 2004/12/02 14:46:52 UTC

DO NOT REPLY [Bug 30858] - [configuration] PropertyConfiguration.save() does not take basePath into account

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=30858>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30858





------- Additional Comments From ebourg@apache.org  2004-12-02 14:46 -------
(In reply to comment #5)
> What can we do about it? I would suggest dropping (deprecating) either the
> get/setURL() or get/setBasePath() methods. The remaining methods should be able
> to deal with both URLs and files. This could be implemented in
> ConfigurationUtils, in a central place. Are there any other ideas/opinions?

The basepath stuff is quite complicated I agree and it's not a part I like to
deal with, however it's still a useful feature and I believe we should keep it.
I'm not favorable to drop the URL, it's the reference to locate the file, I see
the basepath and the filename as byproducts of the URL.

I placed the utility methods getBasePath and getFileName in ConfigurationUtils
but this may not be the best place for them. The logic dealing with paths and
urls may be best placed in AbstractFileConfiguration.



-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org