JNDI Lookup of Datasource

[Edmund Yong]

We have a datasource called DBPool defined in a WebLogic server. On the same server, we want to run a stand-alone program to access the same datasource. The stand-alone program uses Spring/Hibernate for the database access. In this stand-alone program, we defined the following:

<bean id="MyDBPool" class="org.springframework.jndi.JndiObjectFactoryBean">
<property name="resourceRef">
<value>true</value>
</property>
<property name="jndiName">
<value>DBPool</value>
</property>
</bean>

When this stand-alone program runs, it will fail in the JNDI lookup. In general, is it possible for a stand-alone program to do a JNDI lookup for a datasource defined in a WebLogic server?

Thanks.

[Emanuel Kadziela]

Is this standalone program able to lookup any other JNDI resources?

[Chris Mathews]

You are running this application outside the context of WebLogic right? So you need to provide addtional information for Spring to do the JNDI lookup... like where to look for the WebLogic Server.

<bean id="MyDBPool" class="org.springframework.jndi.JndiObjectFactoryBean">
  <property name="jndiEnvironment">
    <props>
      <prop key="java.naming.factory.initial">weblogic.jndi.WLInitialContextFactory</prop>
      <prop key="java.naming.provider.url">t3://localhost:7001</prop>
      <prop key="java.naming.security.principal">username</prop>
      <prop key="java.naming.security.credentials">password</prop>
    </props>
  </property>
  <property name="jndiName">
    <value>DBPool</value>
  </property>
</bean>

The username/password properties would only be required if you are accessing a resource that is secured in WebLogic... in other words it depends on your particular configuration.