Use of classpath*: / Windows

[Cantor, Scott]

On 6/22/15, 4:37 PM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:


>> That's your objection to this, then ? (Not arguing)
>
>Part of it. It's taking a Spring mechanism they only implement in an isolated way and broadening it. If we need something they don't do, it shouldn't overload something they already do in a different way.

This is kind of not true, as it turns out, but somehow I'm even more uncomfortable as a result.

The Spring contexts do automatically implement classpath*: for getResource() lookups, because if they didn't, none of our generic contexts would have worked. For example, the ones that load the credentials handle classpath*:/credentials/idp-signing.key with no teaching by us (those aren't web contexts, just generic, which you didn't modify).

I proved this by trying to change classpath*: to multi-classpath:, but since we only modified the WebAppContext hierarchy, this isn't enough, the generic ones fail. We'd have to teach Spring about a new scheme to make something new work, and I don't want to do that.

So the confusing thing here is really why this doesn't work automatically for SWF use, but it obviously isn't using the Spring APIs it should be or it would work. Either way, it looks like the answer is what we already said, adding a second property and making that one carry the classpath*: syntax. Hopefully that doesn't create yet more problems.

-- Scott