LDAP defaults

[Cantor, Scott]

On 10/1/15, 5:32 PM, "dev on behalf of Nate Klingenstein" <dev-bounces at shibboleth.net on behalf of ndk at internet2.edu> wrote:
>
>That makes sense.  Is there a reason why the defaulting here is done with Spring versus somewhere else like most of the others?

Because you can't use an expression that might contain an undefined property unless it's defaulted (that's why the problem exists with those other properties if you comment them out even when they aren't being used).

If you comment out the property the second one is assigned to be, and it has no default inline, it would fail. Having the default in the property file is because the property itself is being used on the RHS of the assignment, just like when they're used in the Spring files.

With booleans, it's a simple fix, you just include the default anywhere the property is used. With properties that point to files and resources, it's not a simple fix. If you default them, and the resource doesn't exist, stuff breaks there. If you don't default them, and you comment them out, the property won't be found and that breaks.

-- Scott