Opinions on "conditional" Spring files

[Cantor, Scott]

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.

I'm not sure if this is better or not, I think there are arguments both ways in terms of clarity over how to do certain things when you don't know where a file is meant to be placed. It's possible this might be limited to the more unusual cases that almost nobody would ever use, but not as much of a concerted effort to remove as many of the rarely used files.

As an example:

There's a way to override very low level MVC beans by creating conf/mvc-beans.xml, which is currently preinstalled by default as an empty Spring file. The alternative is to not create that file by default but the IdP would load it if it's present. In the log, you get some INFO-level indications when a conditional file is "skipped" because it's not created.

I'm happy that it's possible, but I'm not wedded to using it necessarily, or perhaps not all that widely, but figured it might be worth asking.

-- Scott