[
https://issues.apache.org/jira/browse/CXF-5114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13704158#comment-13704158
]
Freeman Fang commented on CXF-5114:
-----------------------------------
Hi,
>From your patch, you wanna copy http cookie header back from response message
>when you use OneWay, however, this way is not guaranteed to work as CXF oneway
>means no block, send request out and back to caller thread and go on, so
>there's no waiting for the response message, if you logic depend on the
>response message when use oneway, you could fail when the server side oneway
>invocation takes long time, that said, when you client side check the http
>cookie header from response message, the response message of oneway may not
>available yet, so you can't do this way.
Actually, if you use CXF server, the session is initialized and maintained on
server side across invocations, I just commit a testcase to demonstrate it.
Freeman
> CXF Client issue when try to handle session for One-Way Operation call
> ----------------------------------------------------------------------
>
> Key: CXF-5114
> URL: https://issues.apache.org/jira/browse/CXF-5114
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime, Transports
> Affects Versions: 2.7.5
> Environment: JDK 1.7.0_25, CXF 2.7.5 for Client , Axis2 for Server
> Reporter: Harsha Thirimanna
> Assignee: Freeman Fang
> Attachments: CXF_patch.patch
>
>
> I am working for a project that base on web service and client. My issue is
> in client side. I created the client using CXF. I wanted to call few
> operation in one service at once. In server side it handle the session so
> when do the first call it return session id and client should pass it to the
> next operation call in same service There may be sequence of operation calls
> in one service at once.
> I got this issue when first operation is one-way. Because after do the first
> call it returns session id, but second call goes to the server as a fresh
> request(no set session id to second request).
> I went through your code and got some fix , I'll attached that fix with
> this.
> This was blocker issue for us really.
> Note : I have handled the configuration in client side to do this as session
> enabled. I confirmed that, because If I do two way operation call , then this
> session handle correctly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
