Here is a quick and useful tip. This was an error I got when I was running a custom java client to query the Oracle Adaptive Case Management API.
|
executing runQueryCase for addtionalJPQLWhereClause: caseHeader.state = 'ACTIVE' and caseHeader.caseDefinitionName like '%%' Exception thrown: failed to unmarshal class oracle.bpm.casemgmt.CaseList; nested exception is: java.io.InvalidClassException: oracle.bpm.casemgmt.persistence.model.CaseStakeHolderMember; local class incompatible: stream classdesc serialVersionUID = 4454729826681704302, local class serialVersionUID = -349197598855774208; nested exception is: java.io.InvalidClassException: oracle.bpm.casemgmt.persistence.model.CaseStakeHolderMember; local class incompatible: stream classdesc serialVersionUID = 4454729826681704302, local class serialVersionUID = -349197598855774208 javax.ejb.EJBException: failed to unmarshal class oracle.bpm.casemgmt.CaseList; nested exception is: java.io.InvalidClassException: oracle.bpm.casemgmt.persistence.model.CaseStakeHolderMember; local class incompatible: stream classdesc serialVersionUID = 4454729826681704302, local class serialVersionUID = -349197598855774208; nested exception is: java.io.InvalidClassException: oracle.bpm.casemgmt.persistence.model.CaseStakeHolderMember; local class incompatible: stream classdesc serialVersionUID = 4454729826681704302, local class serialVersionUID = -349197598855774208 |
From a sort-of related metalink on Oracle which says :
|
<span id="kmPgTpl:sd_r1:0:dv_rDoc:ot71" class="kmContent">Although the problem couldn't be recreated by the development team on demand, from the exception is clear that the root cause of the problem is the differnce of the version of the org.eclipse.persistence jar distributed with Oracle JDeveloper and Oracle WLS.</span> |
I figured this was something to do with the version of eclipselink libraries currently Read more about How to fix java.io.InvalidClassException error when accessing Oracle ACM Case API via JDeveloper[…]