Datasource exception during Spring initialization

[J Mahayni]

I am interested in catching an exception during Spring initialization but I am not sure of how to do so. I am using Spring to initialize a datasource in the applicationContext.xml as below:
"
<bean id="dataSource" class="org.springframework.jndi.JndiObjectFactoryBean">
<property name="jndiName">
<value>jdbc/ITLM</value>
</property>
</bean>
"

I am getting the following exception that I already resolved but want to capture it for future "setup" occurrance:

"The following exception was logged org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dataSource' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Initialization of bean failed; nested exception is javax.naming.NameNotFoundException: Context: servers/server1, name: jdbc/ITLM: First component in name ITLM not found.
Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL mg.org/CosNaming/NamingContext/NotFound:1.0"

I thought of using ServletContextListener but was not sure of how to capture an exception in the contextInitialized() method? I may need a different approach altogether?

Any ideas are greatly appreciated. Thanks.

[ January 03, 2006: Message edited by: J Mahayni ]

[ January 03, 2006: Message edited by: J Mahayni ]
[ January 04, 2006: Message edited by: J Mahayni ]

[A Kumar]

Hi,

In our case...

<bean id="dataSource" class="org.springframework.jndi.JndiObjectFactoryBean">
<property name="jndiName"><value>java:/test</value></property>
</bean>


java:/test is defined elsewhere in another xml file ...

[J Mahayni]

Thanks for your reply. What I am actually looking for is a way to catch the exception so that I can inform the user of the problem.

[Shrinivas Mujumdar]

There is some Root class available in Spring (I don't remember name of the class) which can give you a root cause of Exception

Just google around for Spring Exception Handling/Spring API docs.

I think question is in wrong forum,but i do not have rights to move the topic.
Shrinivas

[J Mahayni]

Thanks for your reply, as well. I am a bit surprised, to tell you the truth, that neither of you had read my question carefully. I already have the exception (see stack above) and I already fixed the cause of the exception. What I am looking for is A WAY to catch this exception should it occur again in the future (i.e.: how and where), so that I can inform the user of what have happened. I hope this makes better sense to any reader.

[tirtha patil]

I am also getting same exception. Can you please help me in resolving the same as you have mentioned that you resolved it.


Thanks!

J Mahayni wrote:I am interested in catching an exception during Spring initialization but I am not sure of how to do so. I am using Spring to initialize a datasource in the applicationContext.xml as below:
"
<bean id="dataSource" class="org.springframework.jndi.JndiObjectFactoryBean">
<property name="jndiName">
<value>jdbc/ITLM</value>
</property>
</bean>
"

I am getting the following exception that I already resolved but want to capture it for future "setup" occurrance:

"The following exception was logged org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dataSource' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Initialization of bean failed; nested exception is javax.naming.NameNotFoundException: Context: servers/server1, name: jdbc/ITLM: First component in name ITLM not found.
Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL mg.org/CosNaming/NamingContext/NotFound:1.0"

I thought of using ServletContextListener but was not sure of how to capture an exception in the contextInitialized() method? I may need a different approach altogether?

Any ideas are greatly appreciated. Thanks.

[ January 03, 2006: Message edited by: J Mahayni ]

[ January 03, 2006: Message edited by: J Mahayni ]
[ January 04, 2006: Message edited by: J Mahayni ]