[
https://issues.apache.org/jira/browse/CMIS-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15516636#comment-15516636
]
Florian Müller commented on CMIS-999:
-------------------------------------
With OpenCMIS 0.14.0, we have switch the JAX-WS implementation from the Sun
JAX-WS to Apache CXF, mainly to support Java 8 properly. Apache CXF is stricter
in several areas, which is good and bad.
Your server doesn't seem to follow the CMIS specification. It says that the
server must return a CMIS Fault in case of an exception. The CMIS Fault
contains a field "code", which is an integer (BigInteger). It's not available
in your server response and so the response is treated as invalid.
I can check if we can make the exception handling more robust, but eventually
you have to fix your server.
> CmisCookieManager: URL or headers are null!
> -------------------------------------------
>
> Key: CMIS-999
> URL: https://issues.apache.org/jira/browse/CMIS-999
> Project: Chemistry
> Issue Type: Bug
> Components: opencmis-client-bindings
> Affects Versions: OpenCMIS 1.0.0
> Reporter: Alexander Ziziko
> Attachments: ExFirst.png, ExSecond.png
>
>
> We use TCK tests to test our .Net-based CMIS server. After migration to
> version 1.0.0 we have got the next exception for SOAP binding:
> "UNEXPECTED_EXCEPTION: Exception: java.lang.IllegalArgumentException: URL or
> headers are null! (AbstractSessionTest.java:180)
> org.apache.chemistry.opencmis.tck.impl.AbstractSessionTest.run(AbstractSessionTest.java:180)
> org.apache.chemistry.opencmis.tck.impl.AbstractCmisTestGroup.run(AbstractCmisTestGroup.java:115)"
> The reason is that we use standard WCF faults in case of server-side errors
> and it seems that some expected headers are not included.
> Version 0.13.0 works without such problems.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
