fixing the crypto factory beans

[Tom Zeller]

>>Personally I would have made Spring treat bare paths as files, but it's
>>not surprising that it doesn't. Too bad they don't let you control that
>>somehow.
>
> This bring Spring, they do, of course. If we built the service
> ApplicationContexts as FileSystemXmlApplicationContexts instead of
> GenericApplicationContexts, the ResourceLoader in the context would treat
> unprefixed paths as file paths, not classpaths.
>
> I'm not sure what the trade off would be for that, or why we're using
> Generic now, apart from that we did it that way in V2.
>
> We could possibly also inject our own ResourceLoader as well, I guess.

Actually, maybe a custom ResourceLoader is the right thing to do,
that's an interesting idea.

I tend to prefer GenericApplicationContexts in order to look for
resources first on the classpath and then the filesystem. But to be
honest, I feel kinda dumb for not getting resource locations right yet
to make it easy to run the code from Eclipse, via the Maven command
line for tests and Jenkins, and then for deployment.