Registering flow locations by pattern on Windows

[Cantor, Scott]

On 8/13/15, 6:06 AM, "dev on behalf of Misagh Moayyed" <dev-bounces at shibboleth.net on behalf of mmoayyed at unicon.net> wrote:



>- When you do, and you’re doing this on windows and not via an installer, it’s common to state that location via backslashes rather than forward slashes.

Bad idea in general. Java libraries don't do well with backslashes, and since Windows supports forward slashes for the most part, you avoid a lot of unnecessary pain by using them, as well avoiding a needless platform difference in documentation and such.

I believe we have attempted to make sure that forward slashes work everywhere they need to.

If we didn't document that for idp.home, we should fix that.

>- This completely breaks SWF, when it attempts to auto-construct ids for flow definitions. It wants to manipulate the path to build a flow id, and it does this by ripping out the basepath from the resource path. Because the base path is
> with “\”, and yet the resource path is located with “/”, the attempt fails. 
>- As a result, none of the AuthN/conditions flows are built. Sad Panda.

Yes, it does. SWF and Spring in general are really bad at path handling and don't seem to test anything on Windows from what the code suggests.

-- Scott