Posted By:
Anonymous
Posted On:
Wednesday, August 14, 2002 05:45 AM
Hi, To use connection pooling through JNDI the code below seems to be enough: Context ctx = new InitialContext(); ocpds = (OracleConnectionPoolDataSource) ctx.lookup("jdbc/pool/OracleDS"); Where does jdbc/pool/OracleDS come from? If it is a naming service that uses file system, as far as I know, there must be jdbc/pool/OracleDS folder hierarchy. But I couldn't find. I also could not find "fscontext.jar" is which required as file system service provider. So I thought that it could not be naming service based on file file system service provider. But when I look at the line
More>>
Hi,
To use connection pooling through JNDI the code below seems to be enough:
Context ctx = new InitialContext();
ocpds = (OracleConnectionPoolDataSource)
ctx.lookup("jdbc/pool/OracleDS");
Where does
jdbc/pool/OracleDS
come from?
If it is a naming service that uses file system, as far as I know, there must be jdbc/pool/OracleDS folder hierarchy. But I couldn't find. I also could not find "fscontext.jar" is which required as file system service provider. So I thought that it could not be naming service based on file file system service provider.
But when I look at the line
Context ctx = new InitialContext();
I see that it cannot be LDAP, COS or RMI either. Because environment hashtable is not passed to InitialContext().
What is going on? Please help me.
Thanks a lot.
<<Less