"Since an ADF application is just a J2EE EAR file, you can also choose to deploy all of the ADF libraries along with your application, too. In that case, you wouldn't need any kind of global ADF installation on the appserver."
- from http://radio.weblogs.com/0118231/2004/02/27.html#a243
Can anyone please offer insight into this statement? I'm deploying to AS 10g with older versions of BC4J/ADF libraries that support existing, deployed applications. I've tried packaging all of the libraries listed here: http://www.oracle.com/technology/products/jdev/howtos/10g/adf_runtime_update_howto.html
into the WAR but I keep running into problems. If I don't include oc4jclient.jar, for example, then I get a java.lang.IncompatibleClassChangeError because the older, shared libraries deployed to the AS are conflicting with the compiled dependency in my application. If I do include oc4jclient.jar then I run into a different exception.
So, how exactly can an ADF application be packaged such that it is fully independent and doesn't have bad interactions with older version of ADF libaries that are already in the shared libraries area of the target application server?
Thank you very much for your time,
Jeff
P.S. This thread was spawned from another thread that started on a different topic. I wanted to give this thread a more appropriate title since the topic shifted. The previous thread is:
298794