How do I use a JNDI datasource in my application?

Question

Not sure how to access the JNDI datasource i setup in my config.xml. I tried to browse it at rmi://localhost:1099/ but it only shows jmxrmi in the tree.
My config.xml looks like
<n1:config xsi:schemaLocation="http://www.bea.com/ns/wlevs/config/server wlevs_server_config.xsd" xmlns:n1="http://www.bea.com/ns/wlevs/config/server" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <netio>
    <name>NetIO</name>
    <port>9002</port>
  </netio>
  <work-manager>
    <name>JettyWorkManager</name>
    <min-threads-constraint>5</min-threads-constraint>
    <max-threads-constraint>10</max-threads-constraint>
  </work-manager>
  <jetty>
    <name>JettyServer</name>
    <network-io-name>NetIO</network-io-name>
    <work-manager-name>JettyWorkManager</work-manager-name>
  </jetty>
  <rmi>
    <name>RMI</name>
    <http-service-name>JettyServer</http-service-name>
  </rmi>
  <jndi-context>
    <name>JNDI</name>
  </jndi-context>
  <exported-jndi-context>
    <name>exportedJndi</name>
    <rmi-service-name>RMI</rmi-service-name>
  </exported-jndi-context>
  <jmx>
    <jndi-service-name>JNDI</jndi-service-name>
    <rmi-service-name>RMI</rmi-service-name>
    <rmi-registry-port>1099</rmi-registry-port>
    <rmi-jrmp-port>9999</rmi-jrmp-port>
  </jmx>
  <transaction-manager>
      <name>transactionmanager</name>
      <!--max-resource-requests-on-server>1</max-resource-requests-on-server>
      <max-resource-unavailable-millis>1000</max-resource-unavailable-millis-->
  </transaction-manager>
  <data-source>   
      <name>hqsqlconn</name>   
      <driver-params>     
        <url>jdbc:hsqldb:hsql://localhost/wlevdb</url>
        <driver-name>org.hsqldb.jdbcDriver</driver-name>
        <properties>
          <element>
            <name>user</name>
            <value>sa</value>
          </element>
          <element>
            <name>password</name>
            <value></value>
          </element>
        </properties>
        <use-xa-data-source-interface>true</use-xa-data-source-interface>   
      </driver-params>   
      <connection-pool-params>     
        <initial-capacity>1</initial-capacity>     
        <max-capacity>5</max-capacity>     
        <test-table-name>test_table</test-table-name>   
      </connection-pool-params>   
      <data-source-params>     
        <jndi-names>
          <element>hqsqlconn</element>
        </jndi-names>
        <global-transactions-protocol>TwoPhaseCommit</global-transactions-protocol>
      </data-source-params> 
  </data-source>
</n1:config>

Answer 1

I see what you are saying.
The JNDI approach should work-we will try to reproduce this internally.
I would recommend leveraging the OSGi service registry, instead of using JNDI, however. The Event Server is a modular server based on OSGi, so one should use the OSGi service registry whenever possible instead of using the jndi registry. Jndi is primarily there to support legacy code that requires Jndi.
Any data sources that you configure are automatically registered in the OSGi service registry. When there is more than one data source they can be distinguished using their name.
There are a couple of options.
If you want to inject a reference to your datasource into a Spring bean, you can use an annotation, @Service, to annotate a setter method on your bean (see my previous post). The container will then inject a reference to the data source into the bean.
You can also put the following in your spring application context file
<osgi:reference id="myDataSource"
interface="javax.sql.DataSource"/>
This creates a bean proxy that references the datasource by looking up the datasource in the OSGi service registry. It works similarly to JndiObjectFactoryBean, but it uses the OSGi service registry instead of the JNDI registry. You can read more about it here
http://www.springframework.org/osgi/specification
(Look in section 3.3)
Hope that helps.
Seth
Edited by swhite at 08/01/2007 6:19 PM