[
https://issues.apache.org/jira/browse/CONNECTORS-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664184#comment-16664184
]
Piergiorgio Lucidi commented on CONNECTORS-1548:
------------------------------------------------
Found the related issue CONNECTORS-1542 about implementing the Version Policy
selection created by [~douglascrp]:
https://issues.apache.org/jira/browse/CONNECTORS-1542
> CMIS output connector test fails with versioning state error
> ------------------------------------------------------------
>
> Key: CONNECTORS-1548
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1548
> Project: ManifoldCF
> Issue Type: Bug
> Components: CMIS Output Connector
> Reporter: Karl Wright
> Assignee: Piergiorgio Lucidi
> Priority: Major
> Fix For: ManifoldCF 2.12
>
>
> While working on the upgrade to Tika 1.19.1, I ran into CMIS output connector
> test failures. Specifically, here's the trace:
> {code}
> [junit] org.apache.manifoldcf.core.interfaces.ManifoldCFException: The
> versioning state flag is imcompatible to the type definition.
> [junit] at
> org.apache.manifoldcf.agents.output.cmisoutput.CmisOutputConnector.addOrReplaceDocumentWithException(CmisOutputConnector.java:994)
> {code}
> Nested exception is:
> {code}
> [junit] Caused by:
> org.apache.chemistry.opencmis.commons.exceptions.CmisConstraintException: The
> versioning state flag is imcompatible to the type definition.
> [junit] at
> org.apache.chemistry.opencmis.client.bindings.spi.atompub.AbstractAtomPubService.convertStatusCode(AbstractAtomPubService.java:514)
> [junit] at
> org.apache.chemistry.opencmis.client.bindings.spi.atompub.AbstractAtomPubService.post(AbstractAtomPubService.java:717)
> [junit] at
> org.apache.chemistry.opencmis.client.bindings.spi.atompub.ObjectServiceImpl.createDocument(ObjectServiceImpl.java:122)
> [junit] at
> org.apache.chemistry.opencmis.client.runtime.SessionImpl.createDocument(SessionImpl.java:1158)
> {code}
> This may (or may not) be related to the Tika code now using a different
> implementation of jaxb. I've moved all of jaxb and its dependent classes
> into connector-common-lib accordingly, and have no specific inclusions of
> jaxb in any connector class that would need it to be in connector-lib.
> It has been committed to trunk; r1844137. Please verify (or disprove) that
> the problem is the new jaxb implementation. If it is we'll need to figure
> out why CMIS cares which implementation is used.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
