Conflict between ApachePOI library Versions in Emailmetadata and Custom Components (Doc ID 1373470.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle Universal Content Management - Version: 10.1.3.5.0 and later   [Release: 10gR3 and later ]
Information in this document applies to any platform.

Symptoms

You have created a custom component that uses a current version of the ApachePOI library. You are also using the UCM EmailMetadata component, which uses an older version of the same library. This is causing a conflict; it looks like Content Server is only seeing the older POI library in the EmailMetadata component.

You see an error like this one when using your custom component:

Content Server Request Failed
Unable to execute service method 'workflowDashboard_file'. (System Error: org.apache.poi.hssf.usermodel.HSSFRow.createCell(I)Lorg/apache/poi/hssf/usermodel/HSSFCell;)
[ Details ]
The service stack for this request is --WORKFLOW_DASHBOARD_FILE (**no captured values**) java.lang.NoSuchMethodError: org.apache.poi.hssf.usermodel.HSSFRow.createCell(I)Lorg/apache/poi/hssf/usermodel/HSSFCell; at com.rcs.workflowdashboard.util.SpreadsheetUtils.convertResultSetToWorkbook(Unknown Source) at com.rcs.workflowdashboard.util.SpreadsheetUtils.writeResultSetToSpreadsheet(Unknown Source) at com.rcs.workflowdashboard.util.ResultSetExportHandler.saveResultSetAsSpreadsheet(Unknown Source) at com.rcs.workflowdashboard.service.WorkflowDashboardFileService.workflowDashboard_file(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at intradoc.common.IdcMethodHolder.invokeMethod(ClassHelperUtils.java:617) at intradoc.common.ClassHelperUtils.executeMethodEx(ClassHelperUtils.java:279) at intradoc.common.ClassHelperUtils.executeMethod(ClassHelperUtils.java:264) at intradoc.server.Service.doCodeEx(Service.java:507) at intradoc.server.Service.doCode(Service.java:472) at intradoc.server.ServiceRequestImplementor.doAction(ServiceRequestImplementor.java:1360) at intradoc.server.Service.doAction(Service.java:452) at intradoc.server.ServiceRequestImplementor.doActions(ServiceRequestImplementor.java:1201) at intradoc.server.Service.doActions(Service.java:447) at intradoc.server.ServiceRequestImplementor.executeActions(ServiceRequestImplementor.java:1121) at intradoc.server.Service.executeActions(Service.java:433) at intradoc.server.ServiceRequestImplementor.doRequest(ServiceRequestImplementor.java:635) at intradoc.server.Service.doRequest(Service.java:1707) at intradoc.server.ServiceManager.processCommand(ServiceManager.java:359) at intradoc.server.IdcServerThread.run(IdcServerThread.java:197)

Disabling the EmailMetadata component fixes the issue, but this is not a viable workaround.

Cause

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