[
https://issues.apache.org/jira/browse/CONFIGURATION-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17680187#comment-17680187
]
Gilles Sadowski commented on CONFIGURATION-828:
-----------------------------------------------
bq. This library should not try to solve a general problem.
I'd agree.
Is there another case where that component tries to outguess the caller?
bq. Enable to register some FileHandlerListener [...] react by throwing some
Exception.
How much better that is (the file is still not saved...)?
Besides, do you mean that the current code does not throw an exception when the
"write" failed?
> Configuration file truncated then there isn't enough disk space for writing
> ---------------------------------------------------------------------------
>
> Key: CONFIGURATION-828
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-828
> Project: Commons Configuration
> Issue Type: Bug
> Components: File reloading
> Affects Versions: 2.8.0
> Reporter: Alla Gofman
> Priority: Major
>
> Please consider:
> 1) Not to create output stream to file in case there is not enough disk space
> for writing it's content in case of save.
> 2) Enable to register some FileHandlerListener in this case to be notified on
> such issue and can react by throwing some Exception.
> The FileHandlerListener.saving(FileHandler handler) method not suitable,
> because called after the file being already truncated.
> * Meanwhile, the workaround is to extend
> DefaultFileSystem.getOutputStream(File file) method.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
