Property syntax collision

[Rod Widdowson]

> Does this overly concern anybody? I don't see that we have a lot of choice
> here regardless of how it clashes with Spring convention.

Not at all.  

'%' has history as being used for symbol dereferencing.  It's unfortunate,
but I don't see that we have a choice - unless of course Spring allows for
escaping, but that is always a nightmare.  

If we wanted to get really cute I suppose we could say

Idp.open.bracket=%{
Idp.close.bracket=}

               ${ldp.open.bracket}uid${idp.close.bracket}@shibboleth.net

But for my money (even if it worked which seems duibious) that is just
pointlessly confusing,  whereas

	%{uid}@shibboleth.net

Is obvious, if slightly weird.  I suppose we could use different braces, or
even double braces, but '%{' '}' works for me.

For completeness I would totally reject the legacy delimiters we used (
'$IDP_ENTITY_ID$' ) as being unworkable and confusing.
 
> The alternative is just to not do properties in the files that might have
> Velocity snippets in them, but that's probably unworkable in the long run
> unless we just stop using Velocity as the macro language for those things.

I don't see it as ever workable.  Consider the attribute resolver
implementation which is stored in SVN and uses property replacement for
passwords, but velocity for the LDAP search.

/Rod