Mostly for Scott: bean load order definition

[Rod Widdowson]

> I've done it sparingly, only when it was apparently not possible to avoid
> declaring a bean. Usually I try and use getObject conditionally. I was
having
> trouble getting that to work in the flow files.

My problem is related in that I would like to define
shibboleth.CustomScriptObject in a similar place so that I can have sensible
defaults for scripting custom object plugins.
The alternative (which is what is currently checked in) is that you need to
add the customBeanRef='shibboleth.CustomScriptObject' explicitly to your
attribute definition.

I completely buy it that if we start peppering our code with assumptions of
overrides we will go mad, particularly given the nested nature of both our
config files and the fact that our Spring Contexts also nest (via the
reloadable service stuff).

But, even then, given what Ian says I'd be inclined to add these two as sort
of exceptions to our rule.  Or perhaps (better) have an implied rule that
this place (line 42 of global-system.xml) is the only place where we can
predefine beans to do it.

R