Last updated on NOVEMBER 22, 2016
Applies to:Oracle WebCenter Portal - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
Oracle WebCenter Framework application uses Customization layers.
Using WebCenter Portal 126.96.36.199 the customization classes (UserCC, SiteCC, ...) were included in the war file.
After patching the WebCenter to version 188.8.131.52.x, this configuration is not possible anymore.
This is explained in the following documentation:
11g Release 1 (11.1.1)
Part Number B31974-03
35.3 Creating a Deployment Profile
The section 35.3.2 states:
If you have customization classes in your application, they need to be configured to be loaded from the EAR-level application classloader and not from the WAR. You will later add these customization classes to the EAR. To make sure the customization classes are not duplicated in the WAR, be sure to select File Groups > WEB-INF/classes > Filters and deselect any customization classes for the WAR. If you are using a customization.properties file, it should also be deselected.
If your application has customization classes, these classes need to be configured so they load from the EAR-level application classloader. In Application Assembly, select the JAR that contains the customization classes and set Path in EAR to lib. You should have created this JAR as described in Section 35.3.1, "How to Add Customization Classes into a JAR." The JAR files containing the customization classes is added to the EAR file's lib directory.
The customization classes have been packaged to a JAR file and this JAR has been added to the EAR deployment profile in the lib directory.
The EAR has the following structure:
|__ CustomizationClassArchive,jar - JAR with Customization layers
The following problem appears now: from classes inside jar we can't use classes from EAR's classpath (we have NoClassDefFoundException error for class oracle.adf.view.page.editor.mode.ModeContext)
From classes inside "portal.war" we can use classes from EAR's classpath.
How do we fix this problem?
The WebCenter Portal Environment has been upgraded to 184.108.40.206.x and JDeveloper to 220.127.116.11.x with the 18.104.22.168.x WebCenter Portal Extensions.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms