cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aki Yoshida (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 10:55:49 GMT

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

Aki Yoshida commented on CXF-5114:
----------------------------------

Hi Freeman,
I was wondering if the robust-inonly option could help this use case.

This option, when activated (i.e., setting the endpoint property "org.apache.cxf.oneway.robust"
to true to activate it at the endpoint), forces the oneway call to be invoked synchronously
at the server side so that the fault, if occurs, can be returned to the caller in the http
response. You could exploit this behavior to make sure that the second call follows the completion
of the service invocation of the first call.

regards, aki
                
> 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