Praneet Mirchandani wrote:
Also, I noticed that while giving the path to a jar, the entire path upto the jar file itself needs to be specified. Did not know about this.
Peter Johnson wrote:I just had a thought - why do you have a dependency on the ojdbc artifact? Are you making calls specify to the Oracle JDBC driver, or are you making standard JDBC calls? Unless you have a good reason to use the Oracle JDBC-specific classes you really should be using standard JDBC, in which case the the JDBC API comes with the JDK and you can remove the dependency on ojdbc.
Praneet Mirchandani wrote:Hi,
Actually if I didnt include the ojdbc jar file, it threw me an error saying that this jar is missing.
So I included it. The project does use a lot of Sql queries etc.