Hi. We tried to change authentication/authorization in our web aplication. We ended with with overriding a few beans and it works OK. We would like to have this feature optional - the xml configuration with overriden beans file will (or won't) exist outside application. Application context points to this config file this way:
Buf one imperfection still remains - the file is required to exist. When it doesn't, the loading of application context generates "Failed to import bean definitions..."
Can this error be somehow supressed? Thanks.
Your other option if you are using 3.1 is to use bean profiles. Assuming the file will only be present in certain environments you can just define those beans within a bean profile.