Genericizing Resources via path prefix

[Cantor, Scott]

On 9/11/13 12:27 PM, "Tom Zeller" <tzeller at dragonacea.biz> wrote:

>Whether we use Spring's or java-support's, I think it will make life
>easier if we provide a Resource implementation which supports the
>"classpath:" and "file:" and maybe "svn:" or "http:" prefixes, so that
>we can change between implementations without having to change class
>names, meaning that we can use one macro like ${resourcePath} and
>maven filtering or whatever pattern replacement we like.

Meaning you don't have to say type="...ClasspathResource" or
type="...FileResource" or whatever.

Yes, that seems attractive, if it's possible.

My inclination from what I've seen so far is that we're going to end up
better off trying to use the Spring Resource abstraction than our own,
even if that "infects" some components with a Spring dependency. Not the
ideal opinion, maybe.

-- Scott