chemistry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Ziziko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CMIS-999) CmisCookieManager: URL or headers are null!
Date Fri, 23 Sep 2016 14:27:20 GMT

    [ https://issues.apache.org/jira/browse/CMIS-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15516589#comment-15516589
] 

Alexander Ziziko commented on CMIS-999:
---------------------------------------

It seems that the main difference is:
0.13
> 17:20:26 DEBUG dings.spi.webservices.CmisWebServicesSpi: Session 47489721-2b03-45a4-a005-7c0abb13a9eb:
Port provider class: org.apache.chemistry.opencmis.client.bindings.spi.webservices.SunRIPortProvider
1.0
> 17:21:09 DEBUG dings.spi.webservices.CmisWebServicesSpi: Session 978d0666-2beb-4326-b08a-a215db0820ef:
Port provider class: org.apache.chemistry.opencmis.client.bindings.spi.webservices.CXFPortProvider



> 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)

Mime
View raw message