Use of classpath*: / Windows

[Rod Widdowson]

> I'm satisfied the current state is the best option, now that the flow base
is a
> separate property, which fixes the Windows issue.

Whilst I'll buy that it has to be like that, I think that it sucks and I'd
prefer to say that it’s the least-worst.  There *must* be a bug in here
somewhere, either in Spring, in Spring Web Flow, or our configuration.

I guess we are saying that we have fixed our configuration to minimise the
damage by introducing idp.webflows, but that "I'll just return the first
one" bodge rankles.

Is the meat of the problem this:

> the problem is that Spring is inconsistent in how it handles
getResources() and getResource(). And 
> the second problem is that SWF is using both (the former for pattern
flows, the latter for system/explicit flows). 

Or this:

> Yes, but, the base-path of the SWF registry/repository needs the * if
> classpath resources are in src/main/resources and test/main/resources
> (multiple disjoint paths).

If I understand the second, it seems to say that SWF is abusing the
semantics of classpath* to mean something completely different, presumably
because it uses  getRelativeResource() which it wants to mean "reset the
search from the top, do not just look relative to the directory that this
resource is in"?

Or is it both?  Is there a sensible RFI/Bug that can be entered for this?
Where 'sensible' means explainable and with a decent chance of being fixed
since it seems to me that this behaviour is now baked into the SWF/Spring
semantics and cannot be changed.

/Rod