I use RmiProxyFactoryBean for using RMI services in my web app. Those services are used for DB synchronization which is triggered by TimerTasks from time to time.
I want my application to be able to start up even when the remote services are not available. I have marked the remote service beans as lazy-init="true" and with this setup it is possible to create the context using ClassPathXmlApplicationContext() from my unit tests even without the remote connection.
But when the application context is created from my web app using ContextLoaderListener filter and WebApplicationContextUtils.getWebApplicationContex t() it fails. It seems it is ignoring the lazy-init flag. :?
How to ensure the creation of application context even if some "non mandatory" beans creation fails?