Nov 8th, 2005, 03:45 PM
Letting Spring go on even though EJB can not be invoked
I have configured a EJB session bean "myBean" using the
Its properties are set as:
This is not a critical EJB remote for the app. The problem is that when
application starts and when EJB server is down application will not start
because this bean can not be instantiated.
Is there any way that I can let application go on without this bean being instantiated. It is used for trivial purposes and the application can live without it being instantiated.
Nov 8th, 2005, 08:03 PM
You can set the bean attribute lazy-init to true. It won't be initialized until retrieved from the context.
Nov 9th, 2005, 01:09 AM
Besieds that, setting "lookupHomeOnStartup" to "false" might also be worth a try. I successfully used this approach in a similar scenario.
Nov 9th, 2005, 06:57 AM
Originally Posted by Andreas Senft
<bean id="myBean" lazy-init="true" class="org.springframework.ejb.access.SimpleRemote StatelessSessionProxyFactoryBean">
<property name="lookupHomeOnStartup" value="false"/>
did the trick.