Make all configuration resources abstract ?

[Cantor, Scott]

On 12/19/13, 1:29 PM, "Tom Zeller" <tzeller at dragonacea.biz> wrote:

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

Not routinely, but certainly some do use the subversion feature, I know
that much.

>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.

Well, I think there are specific cases where that might not be needed but
if it's applicable to using files, then I don't see any harm in it.

>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.

Pointer? I'm not sure I follow without seeing an example.

>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.

They would typically do that via subversion resources today, I think. I
don't think using a jar is attractive, unless you're doing some kind of
Java appliance maybe.

-- Scott