cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-5114) CXF Client issue when try to handle session for One-Way Operation call
Date Wed, 10 Jul 2013 12:31:48 GMT

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

Daniel Kulp commented on CXF-5114:
----------------------------------

Freeman,

Per jaxws spec with HTTP, the call from the client side *IS* blocking until the 202 response
comes back.  Thus, copying any cookies over is likely the correct thing to do on the client
side.

That said, with a CXF server, if you don't use an interceptor or similar to initialize the
session prior to the OneWayInInterceptor being called, the response likely would not have
a session cookie in it.  You certainly could not wait until the service is invoked to have
the session created.


                
> 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

Mime
View raw message