Make all configuration resources abstract ?

[Tom Zeller]

I guess my questions are : do we want to make all configuration
resources abstract ? do deployers really use non-file:// resources ?

The work item is IDP-348, moving configuration resources out of the
testbed and back into the idp-conf project.

The notion I had was to replace locations of the form
"file://${idp.home}/conf/..." with "${idp.confDir}/conf/..." so that
resources paths would be strings prefixed with file: or classpath: or
even jar: suitable for property replacement.

A stumbling block was that some elements in our Spring bean definition
files expect a File to be injected, and I was wondering if it was
worth the time to abstract File to Resource in general.

I was thinking a deployer might deploy their configuration, managed by
version control, as a jar to be dropped into a container along with
the war.

It looks like in V2 we default to file system resources, wondering if
we should make all resources abstract for 3.0 or later if at all.

Thanks.