please help me

[ramya chandran]

hi all,
i am using mssqlserver4 driver to connect to database..
i have set the properties in weblogic.properties file..
i have also set
weblogic.jdbc.datasource.myDatasource=SQLPOOL..
where SQLPool is my connection pool name..
1.now tell me.."mydatasource" becomes the JNDI name
which has to be connected as
javax.sql.Datasorce ds=(javax.sql.datasource) ctx.lookup("mydatasource");
i have followed these steps but when i run the code..
it just prints
"mydatasource"
and stops...why so?
Does the Jndi name has to be given according to the directory structure or..so
like
weblogic.jdbc.datasource.weblogic.jdbc.jts.SQLPool=SQLPool..
i am confused...
is mssqlserver a txdadatasource or just datasource..
please help me

[Anonymous]

in a former project i used the same driver as you i don't know if it helps but are my settings:

weblogic.jdbc.connectionPool.SQLPool1=\
      url=jdbc:weblogic:mssqlserver4:ip3_1@dt026:1433,\
      driver=weblogic.jdbc.mssqlserver4.Driver,\
      loginDelaySecs=2,\
      initialCapacity=1,\
      maxCapacity=5,\
      capacityIncrement=2,\
      allowShrinking=true,\
      shrinkPeriodMins=15,\
      refreshTestMinutes=1,\
      testTable=sysusers,\
      props=user=sa;password=sa
weblogic.jdbc.DataSource.PuilaetcoDataSource=SQLPool1
weblogic.allow.reserve.weblogic.jdbc.connectionPool.SQLPool1=everyone

and i get acces to this by to the connection by using this

private void createNewConnection() throws SQLException 
{
     try 
      {
       Context ctx = null;
       Hashtable ht = new Hashtable();
       ht.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
       ht.put(Context.PROVIDER_URL,"t3://localhost:7001");
       ctx = new InitialContext(ht);
       javax.sql.DataSource ds = (javax.sql.DataSource) ctx.lookup ("PuilaetcoDataSource");
       this.connection = ds.getConnection();
      }
      catch (SQLException sqle) 
      {
        throw new SQLException();
      }
      catch (NamingException ne) 
      {
        throw new SQLException();
      }
 }

So i don't write this code but i know that it works
------------------
Benjamin l�onard
www.evisor.com