Opinions on "conditional" Spring files

[Rod Widdowson]

> I've managed to wire in the ability to take some of the "occasionally used by advanced deployers" Spring files and potentially
turn them
> into "conditional" imports in the IdP so that the files don't have to be pre-installed and clutter the configuration tree and
could be created
> only if needed by a deployer.

Bearing in mind always that I am not a deployer, or at best an occasional one, I think I actually prefer having (functionally) empty
placeholder files in the deployer's config space.  It sort of leads one towards doing things the right way without having to find
out in the documentation how to do it.  At the same time, with less developer presence in the users' list people might waste
someones time until they hit on the/a right way to do something.

Against that of course is the fact that people do get overwhelmed by the sheer number of files that we give them to play with.  It
seems to me that because of the inherent complexity, people tend to put all their beans in globals.xml rather than exploiting the
locality (and hence reloadability) available to them.

Finally if we went this way we'd need to think through the installer (strictly speaking the ant script) implications carefully.  It
won't be rocket science but it will need some test and thought.  And I hate having to crack that file open....

R