How to Use the OC4J Class Loading Framework to Avoid the Toplink/Jlib/Antlr.Jar to be Loaded in an OC4J Instance? (Doc ID 414761.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Containers for J2EE - Version: 10.1.3.0.0 to 10.1.3.1.0
Information in this document applies to any platform.

Goal

The toplink/jlib/antlr.jar has conflicts with some of the classes in hibernate jar,
and removing the antlr.jar file in the OC4J standalone solved the problem,
but now when deploying the application to Enterprise Edition, there are the same conflicts.
The Toplink libraries are part of the OC4J system shared library and cannot be omited in the classload process by default.
In order to avoid conflicts with the hibernate.jar file, it is needed to avoid the antlr.jar file.
How to avoid the loading of the antlr.jar file by the OC4J instance where the application is deployed?

Solution

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