[
https://issues.apache.org/jira/browse/VFS-587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Labrot updated VFS-587:
-------------------------------
Description:
{{DefaultFileSystemManager}} holds a {{FileProvider}} map.
It casts the FileProvider to an {{AbstractFileProvider}} in methods:
* {{#_closeFileSystem}} to calll {{AbstractFileProvider#closeFileSystem}}
* {{#freeUnusedResources}} to calll
{{AbstractFileProvider#freeUnusedResources}}
Thus it is not possible to implement a {{FileProvider}} which does not extend
{{AbstractFileProvider}}.
Is it possible to move into {{FileProvider}} the two methods
{{closeFileSystem}} and {{freeUnusedResources}} ?
was:
{{DefaultFileSystemManager}} holds a {{FileProvider}} map.
It casts the FileProvider to an {{#_closeFileSystem}}
> Remove all cast to AbstractFileProvider From FileProvider
> ---------------------------------------------------------
>
> Key: VFS-587
> URL: https://issues.apache.org/jira/browse/VFS-587
> Project: Commons VFS
> Issue Type: Task
> Reporter: Nicolas Labrot
>
> {{DefaultFileSystemManager}} holds a {{FileProvider}} map.
> It casts the FileProvider to an {{AbstractFileProvider}} in methods:
> * {{#_closeFileSystem}} to calll {{AbstractFileProvider#closeFileSystem}}
> * {{#freeUnusedResources}} to calll
> {{AbstractFileProvider#freeUnusedResources}}
> Thus it is not possible to implement a {{FileProvider}} which does not extend
> {{AbstractFileProvider}}.
> Is it possible to move into {{FileProvider}} the two methods
> {{closeFileSystem}} and {{freeUnusedResources}} ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
