[
https://issues.apache.org/jira/browse/CMIS-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030768#comment-13030768
]
Baptiste Mesta edited comment on CMIS-366 at 5/9/11 3:23 PM:
-------------------------------------------------------------
I found a solution on the version 0.3.0
It's not really great so if you have a better ideas don't hesitate to tell me.
As workaround I implemented my StandardAuthenticationProvider that extends the
original one and add in the headers of the request the result of the method
getUser()
I also implemented a CookieManager that returns the good cookie depending on
the user id put in headers of the request.
was (Author: baptiste.mesta):
I found a solution on the version 0.3.0
> Cookie are not handled by the client
> ------------------------------------
>
> Key: CMIS-366
> URL: https://issues.apache.org/jira/browse/CMIS-366
> Project: Chemistry
> Issue Type: Improvement
> Components: opencmis-client-bindings
> Affects Versions: 0.2.0-incubating, OpenCMIS 0.3.0
> Reporter: Baptiste Mesta
> Assignee: Florian Müller
> Fix For: OpenCMIS 0.4.0
>
>
> The client does not handle cookie.
> Some cmis servers use cookies to handle session. If the http request do not
> have the cookie, the server is creating new session for each call and that
> make it having a LOT of sessions if there is a lot of calls.
> I think having the client save cookie in the client session and put it in
> each request is very important.
> I'll submit a patch soon to fix this.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
