Use of classpath*: / Windows

[Tom Zeller]

>> I put quotes around 'needed' because, of course, in the idp-conf tests
>> we create a flow repository/registry (I forget which) specific for
>> each test. However, for local storage, I want to test using a browser,
>> which we don't do in the idp-conf tests.
>
> Is that you manually, or the integration tests?

Manually via the testbed, automatically via integration tests.

>> There are other ways to do what I did, which essentially is just
>> loading a flow into the IdP. But it seemed like supporting classpath*:
>> was a good-idea, especially if we want to move system flows into a
>> JAR.
>
> It's not the same though, as we said in the bug. For Spring, that means "load every file it can find", but for SWF, loading a flow has to load exactly one file.

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). The resource loader "hack" I added does
what you say above, reverses the * to just-one.

Maybe a distinct property for the SWF base-path is what we want, but
I'm not really suggesting that.

> Anyway, if I have to manually run the LS flows to trigger this, that's what I was looking for, I couldn't remember.

Rod asked me to add a link to the testbed, I can do that.