Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

"Base type ID property not set!" error when browsing CMIS folder

SA-35270

Summary



An issue integrating a CMIS external repository in a Pega Application
The following error message occurs when clicking the "Browse" button in the "Integration & security" tab of the Application Rule form:

.pyCMISTreeNodes(1): Unable to load children for the / folder at this time:

Error Messages



The following error message appears on screen:
.pyCMISTreeNodes(1): Unable to load children for the / folder at this time:

The following exception is printed in the logs:

com.pega.pegarules.pub.services.ConnectorException: Caught unhandled exception
at com.pegarules.generated.activity.ra_action_invoke_22cccd40e60f34b483297b1a1f47b925.step7_circum0(ra_action_invoke_22cccd40e60f34b483297b1a1f47b925.java:1001)
at com.pegarules.generated.activity.ra_action_invoke_22cccd40e60f34b483297b1a1f47b925.perform(ra_action_invoke_22cccd40e60f34b483297b1a1f47b925.java:173)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3553)
at com.pegarules.generated.activity.ra_action_pycmisconnector_e7724d8fe9fde0de690673f3b4d046ae.step9_circum0(ra_action_pycmisconnector_e7724d8fe9fde0de690673f3b4d046ae.java:898)
at com.pegarules.generated.activity.ra_action_pycmisconnector_e7724d8fe9fde0de690673f3b4d046ae.perform(ra_action_pycmisconnector_e7724d8fe9fde0de690673f3b4d046ae.java:219)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3553)
at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(Executable.java:10711)
at com.pegarules.generated.activity.ra_action_pygetfoldertree_aab1dc54513f08174efde13f3adb491e.step1_circum0(ra_action_pygetfoldertree_aab1dc54513f08174efde13f3adb491e.java:165)
at com.pegarules.generated.activity.ra_action_pygetfoldertree_aab1dc54513f08174efde13f3adb491e.perform(ra_action_pygetfoldertree_aab1dc54513f08174efde13f3adb491e.java:70)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3553)
at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(Executable.java:10711)
at com.pegarules.generated.activity.ra_action_pygetcmisfoldertreenodes_7c8679276923aed18b812fc011e5a170.step6_circum0(ra_action_pygetcmisfoldertreenodes_7c8679276923aed18b812fc011e5a170.java:642)
at com.pegarules.generated.activity.ra_action_pygetcmisfoldertreenodes_7c8679276923aed18b812fc011e5a170.perform(ra_action_pygetcmisfoldertreenodes_7c8679276923aed18b812fc011e5a170.java:171)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3553)
at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(Executable.java:10711)
at com.pegarules.generated.activity.ra_action_pycmistreenodespreload_0e1727dcbf6a9f1fa0671f5577a04d84.step5_circum0(ra_action_pycmistreenodespreload_0e1727dcbf6a9f1fa0671f5577a04d84.java:491)
at com.pegarules.generated.activity.ra_action_pycmistreenodespreload_0e1727dcbf6a9f1fa0671f5577a04d84.perform(ra_action_pycmistreenodespreload_0e1727dcbf6a9f1fa0671f5577a04d84.java:153)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3553)
at com.pegarules.generated.callActivity_071027_yoB3RheCwDdLlLDKhZ4s2w.callActivity07_10_27(callActivity_071027_yoB3RheCwDdLlLDKhZ4s2w.java:133)
at com.pegarules.generated.callActivity_071027_yoB3RheCwDdLlLDKhZ4s2w.invoke(callActivity_071027_yoB3RheCwDdLlLDKhZ4s2w.java:80)
at com.pega.pegarules.generation.internal.library.LibraryRuntime.resolveAndinvokeFunctionViaReflection(LibraryRuntime.java:221)
at com.pega.pegarules.generation.internal.library.LibraryRuntime.invokeLibraryRuntime(LibraryRuntime.java:119)
at com.pega.pegarules.session.internal.mgmt.Executable.invokeLibraryRuntime(Executable.java:9105)
at com.pega.pegarules.priv.generator.LibrarySupport.resolveAndInvokeFunctionViaReflectionWithException(LibrarySupport.java:275)
at com.pegarules.generated.flowaction.ra_action_pzcmistreedisplay_9bcecf22174d735086bda8eb1a284668.RunFlowActionActivity_circum0(ra_action_pzcmistreedisplay_9bcecf22174d735086bda8eb1a284668.java:328)
at com.pegarules.generated.flowaction.ra_action_pzcmistreedisplay_9bcecf22174d735086bda8eb1a284668.perform(ra_action_pzcmistreedisplay_9bcecf22174d735086bda8eb1a284668.java:73)
at com.pega.pegarules.session.internal.mgmt.Executable.doAction(Executable.java:3358)
at com.pegarules.generated.activity.ra_action_performpreprocessing_e6b3b65d6cb30cfcf9e810702cbc668a.step1_circum0(ra_action_performpreprocessing_e6b3b65d6cb30cfcf9e810702cbc668a.java:177)
at com.pegarules.generated.activity.ra_action_performpreprocessing_e6b3b65d6cb30cfcf9e810702cbc668a.perform(ra_action_performpreprocessing_e6b3b65d6cb30cfcf9e810702cbc668a.java:70)
...
Caused by: java.lang.IllegalArgumentException: Base type ID property not set!
at org.apache.chemistry.opencmis.client.runtime.repository.ObjectFactoryImpl.convertObject(ObjectFactoryImpl.java:594)
at org.apache.chemistry.opencmis.client.runtime.SessionImpl.getObject(SessionImpl.java:523)
at org.apache.chemistry.opencmis.client.runtime.SessionImpl.getRootFolder(SessionImpl.java:710)
at org.apache.chemistry.opencmis.client.runtime.SessionImpl.getRootFolder(SessionImpl.java:704)
at com.pega.pegarules.integration.engine.internal.connect.cmis.CMISConnector.getFolderTree(CMISConnector.java:3209)
at com.pega.pegarules.integration.engine.internal.connect.cmis.CMISConnector.invokeService(CMISConnector.java:2034)
at com.pega.pegarules.integration.engine.internal.connect.cmis.CMISConnector.invoke(CMISConnector.java:1336)
at com.pega.pegarules.integration.config.internal.connect.PRConnectorFactory.invokeConnector(PRConnectorFactory.java:82)
at com.pega.pegarules.integration.engine.internal.util.PRConnectorUtilsPriv.invokeConnector(PRConnectorUtilsPriv.java:168)
at com.pega.pegarules.session.internal.mgmt.Executable.invokeConnector(Executable.java:11248)
at com.pega.pegarules.integration.engine.internal.util.PRServiceUtils.invokeCMISConnector(PRServiceUtils.java:3322)
at com.pegarules.generated.activity.ra_action_invokecmisconnector_7845e63814edcb0f311146f606b05327.step1_circum0(ra_action_invokecmisconnector_7845e63814edcb0f311146f606b05327.java:171)
at com.pegarules.generated.activity.ra_action_invokecmisconnector_7845e63814edcb0f311146f606b05327.perform(ra_action_invokecmisconnector_7845e63814edcb0f311146f606b05327.java:70)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3553)
at com.pegarules.generated.activity.ra_action_invoke_22cccd40e60f34b483297b1a1f47b925.step7_circum0(ra_action_invoke_22cccd40e60f34b483297b1a1f47b925.java:947)
... 97 more




Steps to Reproduce

  1. Deploy a Pega 7 Application in WebLogic 12c
  2. Configure the RULE-CONNECT-CMIS Connector to point to a CMIS repository
  3. Configure the Application to use the CMIS connector above.
  4. Click on the Browse button and observe the error messages above appearing on screen and in the logs

Root Cause



A third-party product issue affecting the library Apache Chemistry embedded in the Product:
  • CMIS-595 – “Fails in Webservices mode with Weblogic12C - Both 0.6 and 0.8 Weblogic exclusive binding jars are tested”

This issue is caused in turn by a bug affecting the EclipseLink Implementation MOXy provided with Oracle WebLogic 12c:

  • Bug 380122 - Error when enum is used with @XmlElementRefs

Resolution



Make the following change to the operating environment:
Restore the standard Glassfish Reference Implementation (RI) JAXB data binding and JAXB providers used in previous WebLogic Server releases as described in "Using the Glassfish RI JAXB Data Binding and JAXB Providers" Oracle WebLogic documentation page.
The recommended approach is to set global server-level databinding and JAXB Providers to use JAXB RI
This can be done in two alternative ways:
  • Applying the entry below to the EXT_PRE_CLASSPATH environment variable:

    export "EXT_PRE_CLASSPATH=$EXT_PRE_CLASSPATH:$WL_HOME/modules/databinding.override_1.0.0.0.jar"

    Check the module path for the right jar name before applying the above change.
  • Setting the following two java system properties:

    export "EXTRA_JAVA_PROPERTIES=$EXTRA_JAVA_PROPERTIES -Dcom.sun.xml.ws.spi.db.BindingContextFactory=com.sun.xml.ws.db.glassfish.JAXBRIContextFactory -Djavax.xml.bind.JAXBContext=com.sun.xml.bind.v2.ContextFactory

Tags:

Pega Platform Pega Platform 7.2.1 Data Integration

Published March 26, 2017 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Visit the Collaboration Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us