"WARNING: Code-source ojdbc14.jar has same filename but is not identical" When Including Different Version of JDBC Library in an Application
Last updated on OCTOBER 13, 2017
Applies to:Oracle Containers for J2EE - Version 10.1.3.3.0 and later
Information in this document applies to any platform.
Checked for relevancy on 18-April-2011
***Checked for relevance on 18-Feb-2015***
There is an issue when trying to use different version of oracle's JDBC driver.
The application is deployed using the option documented in:
Chapter 3 Utilizing the OC4J Class Loading Framework
Oracle® Containers for J2EE Developer's Guide 10g (10.1.3.1.0)
"Using a Packaged JAR Instead of an Oracle Shared Library
The class loading infrastructure enables you to package an XML parser or JDBC
driver as a JAR with your application and then force the application to use
it instead of the Oracle XML parser or JDBC driver installed with OC4J,
without having to declare the JAR as a shared library within OC4J
This action caused the following errors :
C:\work\tools\oc4j\j2ee\home\applications\application\application\WEB-INF\lib\ojdbc14.jar (fromWEB-INF/lib/ directory in
C:\work\tools\oc4j\j2ee\home\applications\application\application\WEB-INF\lib) has the samefilename but is not identical to /C:/work/tools/oc4j/jdbc/lib/ojdbc14dms.jar (from<code-source> (ignore manifest Class-Path) in META-INF/boot.xml in
C:\work\tools\oc4j\j2ee\home\oc4j.jar). If it contains different versions of the same classes, it will be masked as the latter is already visible in the search path of loaderapplication.web.application:0.0.0.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms