JDBC Thick connection using ADF

Question

Hi All,
I am doing Thick Oracle connection using ADF but i am getting this error...
java.lang.UnsatisfiedLinkError: no ocijdbc11 in java.library.path
following is my code..
try {
Class.forName("oracle.jdbc.OracleDriver");
Connection con=DriverManager.getConnection("jdbc:oracle:oci8:@dbndevp", "mfonline", "mfonline");
System.out.println(con.isValid(1));
} catch (Exception e) {
e.printStackTrace();
So how can i do it in ADF......
-Thanks
Edited by: Santosh Vaza on Dec 31, 2010 6:14 PM

Answer 1

Suppose i have a backing bean class then how would i get connection to database, Suppose that i am using 2 connections to 2 different database.Case 1: If you are using ADF Business Components (or some other framework that implements "business services" layer)
In this case ADF BC implement the "business services" layer in the application architecture and they are responsible for the interaction with the DB. You should encapsulate there all the program logic that interacts directly with the DB. You can invoke ADF BC methods from managed beans but you should not implement any direct DB operations in managed beans (in particular you should not open DB connections, parse and execute SQL statements in managed beans). If you need to work with 2 different databases, then you have to define 2 different ApplicationModules (with connections to these databases). There is an important disadvantage - ADF BC does not support global transactions (e.g. XA-compatible transactions), so if you need distrubuted transactions, then either you could use DB-links (if both databases are Oracle ones) or you will need a different framework.
Case 2: If you are not using any framework that implements "business services" layer
In this case you should not use DriverManager, but you could get DB connections from JDBC DataSources. In this way you would benefit from the connection pooling of the DataSources and you would avoid the heavy overhead of creating and closing DB connections. (When you close a DB connection acquired from a DataSource, in fact it is not closed but it is just checked back into the DataSource's connection pool).
Dimitar