Registering flow locations by pattern on Windows

[Misagh Moayyed]

Well, it does seem like the Idp is normalizing paths only when idp.home is
missing and then discovered automatically. My proposal would be to do the
same regardless; that will fix the problem. It may be fair to put the onus
on deployers and expect them to provide the normalized correct value,
instructing them to read the docs to figure out why having seen that
warning, etc. An easier thing is to do what the idp does already, but
extend it to all cases and normalize all, [which is a funny term because
of course some paths may be abnormal, due to bad parenting and may have
psychological issues :)]

> -----Original Message-----
> From: dev [mailto:dev-bounces at shibboleth.net] On Behalf Of Rod Widdowson
> Sent: Thursday, August 13, 2015 6:11 AM
> To: 'Shib Dev' <dev at shibboleth.net>
> Subject: RE: Registering flow locations by pattern on Windows
> 
> > Specifically those that run on Windows? I am running this with IdP
> 3.1.3-SNAPSHOT; I see the Windows Installer corrects this issue by
> specifying "/"s instead.
> 
> No (or if I did it was part of the one-off pain), I learnt long ago not
to
> meddle in the affairs of (a) separators and (b) classpaths because they
> are subltle and quick to anger.
> 
> My approach has always been to just accept that it sucks, that Oracle
> really doesn't want you to run Java on a Microsoft product (is java.dll
> still not
> rebased?) and you have to live with the pain if you want to run on
> Windows.
> The Installer actually has an explicit action to create a "java-ized"
> idp.home because in many cases only forward slashes will do and in
others
> only back will do. I suppose I'm glad that I don't need a third with the
> back slash quoted...
> 
> I suppose that we might add a warn somewhere if there was a backslash in
> idp.home. (not that that isn't a valid Posix name of course)
> 
> R
> 
> 
> 
> --
> To unsubscribe from this list send an email to dev-
> unsubscribe at shibboleth.net