JNDI obj not binding to initial context--10gRel 2 issue only,works in rel3

Question

hi all,
The issue I am writing about is an issue only in OAS 10g release 2 (10.1.2.0.2) and not in release 3. I have an issue where in I am trying to bind a data source object to the initial context. This data source object reference is created dynamically and is not specified in any XML file (say like web.xml or server.xml). The business requirement driving this is that for each user we need to create a data source dynamically and attach it to the JNDI and then this JNDI name is passed on to Crystal Reports which will use this data source to retrieve its data from the DB. The code for creating the data source dynamically is as below,
private String setDataSource(String username, String password) throws NamingException {
          String prefix = "jdbc";
          InitialContext ic = new InitialContext();
          // Construct BasicDataSource reference
          Reference ref = new Reference("javax.sql.DataSource", CustomDataSourceFactory.class.getName(), null);
          ref.add(new StringRefAddr("url", xxxxxx));
          ref.add(new StringRefAddr("schema",xxxxx));
          ref.add(new StringRefAddr("xxxxxx", xxxxx));
          ref.add(new StringRefAddr("password", xxxxx));
          try {
               ic.listBindings(prefix);
          } catch (NameNotFoundException exp) {
               ic.createSubcontext(prefix);
          String datasourceName = prefix + "/" + oneNumber;
          ic.rebind(datasourceName, ref);
          return datasourceName;
As you can see the reference to the data source is added dynamically. Now when I try to obtain this object by looking up the context for its JNDI name I get a object not found error. This is how I look up the object through my code,
private void testDataSource(String dsName){
          Connection conn = null;
          Statement stmt = null;
          ResultSet rs = null;
          try {
               InitialContext ic = new InitialContext();
               javax.sql.DataSource ds = (javax.sql.DataSource) ic.lookup(dsName);
               conn = ds.getConnection();
               stmt = conn.createStatement();
               rs = stmt.executeQuery("select sysdate from dual");
               String result = rs.getString(1);
               System.out.println("----YOGI----Result of query execution is AAA -----" + result);
          } catch (Exception ex ){
               System.out.println("----YOGI----the exception from this specific block is " + ex.getLocalizedMessage());
          finally {
               try {
                    if (null!= rs)
                         rs.close();
                    if(null !=stmt)
                         stmt.close();
                    if(null !=conn)
                         conn.close();          
               } catch (Exception ex){
                    System.out.println("Hopeless");
When I do this I get this exception message --> jdbc/1562 not found in MyAPP
jdbc/1562 is the data source JNDI name I generated in the first method and "MyAPP" is the name of my application. I decided to make the JNDI globally available in the context and hence I used "java:global/jdbc/1562" for my datasource name and even that did not work even though the JNDI name is not bound to the application in specific.
I am really at a loss here as this is a simple add/retrieve operation to a object bound to the context. Can someone tell what is wrong here? The same code works fine in release 3 OAS and also in tomcat and websphere. Any help will be appreciated.
Regards,
Yogi

Answer 1

OK, I seem to be getting a new exception, not sure if I did any change but ran into this exception in the logs,
11/08/24 18:45:08 ----YOGI----the exception from this specific block is javax.naming.Reference cannot be cast to javax.sql.DataSource*
From what I read on the web, this is prevalent in glassfish and jboss. The reason could be that missing j2ee.jar in classpath or duplicate jdbc jars. I added j2ee.jar to my application library in oc4j dint resolve the issue. I removed jdbc jar from the OAS lib folder and restarted, it dint help.
Any other clues, anyone?