[
https://issues.apache.org/jira/browse/JAMES-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518996
]
Stefano Bagnara commented on JAMES-803:
---------------------------------------
I wrote the FileSystem service to encapsulate the service and remove some
avalon specific dependency from most modules.
I think the best approach to this change would be:
1) Add the getResource method to the interface that simply return an
InputStream instead of a file.
2) Create the default implementation of the avalon file system to call the
getFile and simply provide the stream for that file
3) Change the FileSystem users to use getResouce instead of getFile when they
don't need a File instance.
Then I would probably leave to the spring implementation the loading of
resources from the classpath: in a phoenix environment IMHO it make sense to
keep using the "phoenix way".
So, this is similar, but done in 2 separate steps (refactoring of the api
first, new features after): what do you think?
> Add ability to load resources from the classpath instead of the file system
> ---------------------------------------------------------------------------
>
> Key: JAMES-803
> URL: https://issues.apache.org/jira/browse/JAMES-803
> Project: James
> Issue Type: Improvement
> Components: James Core
> Affects Versions: Trunk
> Reporter: Zsombor
> Priority: Minor
> Attachments: loading-from-the-classpath-spring.patch,
> loading-from-the-classpath.patch
>
>
> Currently lots of components try to get their configuration files from the
> filesystem, but most of the time it's simpler to get from the classpath.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
