AS904: JDBC classpath problem in OC4J instance

Question

Hi,
I want to run an ADF Faces web app in AS 904 (WAR contains all JAR incl. JDBC JARs). It does not work because the the application uses a newer version of the JDBC JARs than the version provided with AS904. The OC4J instance seems to load the older JDBC version instead of the JDBC version provided with the WAR.
The classpath of the AS904 OC4J instance defined in application.xml does not include any JDBC JARs.
This fact seems to be the root of all the trouble!
Is there a way to change the classpath for the JDBC JARs of my OC4J instance without affecting other OC4J instances?
Markus

Answer 1

Thanks Avi!
I can' solve my problem because the CLASSPATH of the OC4J-instance has a fixed prefix definition. Changing the CLASSPATH in application.xml oder with a cmd switch like -cp "my class path" only affects the CLASSPATH behind the prefix.
The prefix is definds in the manifest file of the oc4j.jar like this:
lib/ejb.jar lib/servlet.jar lib/ojsp.jar lib/jndi.jar lib/
jdbc.jar iiop.jar iiop_gen_bin.jar lib/jms.jar lib/jta.jar lib/jmxri
.jar lib/javax77.jar lib/javax88.jar ../../opmn/lib/ons.jar ../../op
mn/lib/optic.jar ../../lib/dms.jar ../../dms/lib/dms.jar lib/connecto
r.jar lib/cos.jar lib/jsse.jar ../../oracle/lib/jsse.jar lib/jnet.ja
r lib/jcert.jar lib/activation.jar lib/mail.jar ../../javavm/lib/jasp
er.zip ../../lib/xmlparserv2.jar ../../oracle/lib/xmlparserv2.jar lib
/jaxp.jar lib/jaas.jar jazn.jar ../../jdbc/lib/classes12dms.jar ../..
/oracle/jdbc/lib/classes12dms.jar ../../jdbc/lib/nls_charset12.jar ..
/../oracle/jdbc/lib/nls_charset12.jar jaxb-rt-1.0-ea.jar ../../soap/
lib/soap.jar ../../webservices/lib/wsserver.jar ../../webservices/lib
/wsdl.jar ../../rdbms/jlib/aqapi.jar lib/jem.jar ../../javacache/lib/
cache.jar lib/http_client.jar ../../jlib/jssl-1_1.jar ../../oracle/jl
ib/jssl-1_1.jar ../../jlib/repository.jar ../../oracle/jlib/repositor
y.jar lib/jaasmodules.jar ../../sqlj/lib/runtime12ee.jar ../../sqlj/l
ib/translator.jar lib/crimson.jar
As you can see, the JDBC lib is loaded with this settings before my CLASSPATH seetings!
I bet changing this manifest file affects Oracle support. ;-)
In the end, my J2EE web application does not run on a J2EE compliant Oracle AS 904!
Thanks,
Markus