|
From: aappddeevv (JIRA) <no...@sp...> - 2010-03-25 00:07:34
|
[ https://jira.springsource.org/browse/RCP-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
aappddeevv updated RCP-630:
---------------------------
Attachment: DefaultImageSource.java
> Allow DefaultImageSource to resolve resources
> ---------------------------------------------
>
> Key: RCP-630
> URL: https://jira.springsource.org/browse/RCP-630
> Project: Spring Rich Client Project
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.1.0
> Environment: all
> Reporter: aappddeevv
> Assignee: Lieven Doclo
> Attachments: DefaultImageSource.java
>
>
> Allow DefaultImageSource to convert string specifications to resources for loading images. Other spring components interpret string arguments as resources depending on the "context" of the string itself e.g. ClassPathXmlApplicationContext interprets string resources as classpath resources by default.
> Change DefaultImageSource to allow values in the imageResources map to be either resources or strings. Strings are converted to resources automatically by allowing DefaultImageSource to inherit from ResourceLoaderAware. We should probably also take map initialization out of the constructor or at least provide an alternative.
> There are other fancier ideas for creating image resolver objects that plug in a strategy for image resolution but this is probably sufficient for now. This also allows the issue around the ResourceMapFactoryBean class being removed in spring 3.0. Users could still use PropertiesLoaderSupport if they wanted to load properties files as well as ResourceMapFactoryBean if they are still on spring 2.5
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.springsource.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|