CDI Doesn't Work for Split-Source Deployment if Unresolved Dependencies Exist In WEB-INF/classes
Last updated on NOVEMBER 05, 2016
Applies to:Oracle Weblogic Server - Version 188.8.131.52 and later
Information in this document applies to any platform.
In WebLogic Server 12.1.1, customers can face issues during the split-deployment phase wherein the deployment fails with a class not found exception when unresolved dependencies are kept in the web project within the scope of Contexts and Dependency Injection (CDI) scanning. These classes can often be classes which are not actively referred to by the application, but still are packaged within the application for some reason. If these classes have imports, references that are unresolved or are not included within the application packaging, and these classes fall in the scope of CDI scanning, the deployment fails with a ClassNotFoundException:
Customer applied the fix for unpublished defect 13587604 to his environment.
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