Config JDBC/DATASOURCE/JNDI for NT 4.0/DB2 6.1/Weblogic 6.0

Question

Hi, i got a problem to access a database "ESAV1" using jdbc. I can do it using
the DriverManager : "try { Class.forName("COM.ibm.db2.jdbc.net.DB2Driver"); String
url = "jdbc:db2://javaserv1:6789/ESAV1"; Connection con = DriverManager.getConnection(url,
"db2admin", "db2admin");
// Create a Statement java.sql.Statement stmt = con.createStatement();
// Select des pays : java.sql.ResultSet rset = stmt.executeQuery("select distinct
NOM, ZONE from ER_PAYS ORDER BY NOM ASC"); ..." This works all right. NOW I want
to use a datsource to optimize the performance of my application. First Problem
: i want to put attributes to my web application (I did on Websphere and it worked).
When i try to configurate them in the web.xml file as context-param, it does not
work : "<web-app> <context-param> <param-name>datasource</param-name> <param-value>ESAV</param-value>
</context-param> <context-param> <param-name>password</param-name> <param-value>db2admin</param-value>
</context-param> <context-param> <param-name>userid</param-name> <param-value>db2admin</param-value>
</context-param>... " When I put directly in my java code (in the "init" method
" of my servlet), it does not work either: "password = (String) this.getServletContext().getAttribute("password");
if (password == null){ password = "db2admin";} userid = (String) this.getServletContext().getAttribute("userid");
if (userid == null){userid = "db2admin";} Hashtable env = new Hashtable(); Context
ctx = null; env.put(Context.PROVIDER_URL, "t3://telajava1:7001 env.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
String dataSrcName =(String) this.getServletContext().getAttribute("datasource");
if (dataSrcName == null) {dataSrcName = "ESAV"; } try { ctx = new InitialContext(env);
String dbJndi = dataSrcName; ds = (DataSource) ctx.lookup(dbJndi); ...." This
gives me null for the attributes "datasource" "userid" and "password" (using getServletContext).
Then when I give them values, the ctx and ds values are : javax.naming.InitialContext@27ff0d
and weblogic.jdbc.common.internal.RmiDataSource@62ba99 but ther is no response
to "...Connection conn = com.eroaming.Controller.ds().getConnection(db2admin,db2admin);
.." and no error message...it just blocks...! If somebody can help me with those
troubles I would be very thankful.
ps : 1.the JDBC Connection Pools Configuration : NAME : driverERoaming URL : jdbc:db2://javaserv1:6789/ESAV1
DRIVER CLASS NAME : COM.ibm.db2.jdbc.net.DB2Driver PROPERTIES : language=fr_FR
2. the JDBC Data Sources configuration : Name: ESAV JDNI NAME :ESAV POOL NAME
:driverERoaming
3. My DataBase Configuration : NAME : ESAV1 user : db2admin password : db2admin
BEA is on the host : telajava1 DB2 is on the host : telaserv1

Answer 1

6.1 did not implement the final version of the Servlet 2.3 specification, that's
          why you see differences.
          http://edocs.bea.com/wls/docs61/notes/new.html#1064420
          Sanjeev <[email protected]> wrote:
          > Hi All,
          > I was using weblogic 6.1 and as my organization wants to go for 7.0, we
          > are in the process of evaluating 7.0 ver.
          > WL6.1 javax.servlet.filter interface provides the methods doFilter(), setFilterConfig(),
          > getFilterConfig(). We have an implementation for the Filter which also contains
          > a private method init(FilterCongig filterConfig).
          > In 7.0 javax.servlet.filter interface the methods are doFilter(), init(), destroy().
          > Because of the obvious reason i have a private implementation of init(FilterConfig
          > )in my code the build does not succeed. When i checked the java specifications
          > from Sun site I found 1.3.1 and 1.4(beta) specs provide doFilter(), init() and
          > destroy().
          > Question is: Is weblogic 6.1, JDK 1.3.1 compliant, if so why there is not init()
          > method in the filter interface??. (Otherwise its a bug)
          > Because of this the porting has become a serious issue as in some cases we need
          > to support both 6.1 and 7.0
          Dimitri