[jira] [Resolved] (CXF-6516) CXF does not obey and ensure the setting of Message.MAINTAIN_SESSION

["Daniel Kulp (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CXF-6516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Kulp resolved CXF-6516.
------------------------------
       Resolution: Won't Fix
    Fix Version/s: Invalid


I don't think this is something we can fix.  When run as an applet, the browser/plugin runtime provides a slightly different HTPUrlConnection that is restricted on what it can do, where it can contact, and what we can set.   

> CXF does not obey and ensure the setting of Message.MAINTAIN_SESSION
> --------------------------------------------------------------------
>
>                 Key: CXF-6516
>                 URL: https://issues.apache.org/jira/browse/CXF-6516
>             Project: CXF
>          Issue Type: Improvement
>          Components: Core, JAX-WS Runtime
>    Affects Versions: 2.7.17
>            Reporter: Valer Micle
>             Fix For: Invalid
>
>
> Hi,
> I have a CXF web-service client running inside an Applet.
> The Applet is assigning by default a JSESSIONID to each request made.
> When i do a new web-service call, I try to manually disable the setting of JSESSIONID to the request like this:
> {code}
> Client wsClient = ClientProxy.getClient(proxyObject);
> wsClient.getRequestContext().put(Message.MAINTAIN_SESSION, false);
> {code}
> However, it seems that CXF does not take the value into account and the same session is used for all request.
> I expect that CXF will invalidate the HttpSession after the call is made.
> It will be great as well if the CXF API will expose the backing HttpSession so that i can manually invalidate the session as needed.
> My use-case is that from the Applet I need to change at runtime the username/password used to connect to the webservice. however, since the same JSESSIONID is used, the new authentication credentials are ignored by the server where I'm connection.
> Thank you



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)