Return-Path: X-Original-To: apmail-cxf-dev-archive@www.apache.org Delivered-To: apmail-cxf-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8D286F332 for ; Tue, 9 Jul 2013 01:14:09 +0000 (UTC) Received: (qmail 78015 invoked by uid 500); 9 Jul 2013 01:14:09 -0000 Delivered-To: apmail-cxf-dev-archive@cxf.apache.org Received: (qmail 77928 invoked by uid 500); 9 Jul 2013 01:14:09 -0000 Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list dev@cxf.apache.org Received: (qmail 77919 invoked by uid 99); 9 Jul 2013 01:14:09 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Jul 2013 01:14:09 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of willem.jiang@gmail.com designates 209.85.220.54 as permitted sender) Received: from [209.85.220.54] (HELO mail-pa0-f54.google.com) (209.85.220.54) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Jul 2013 01:14:03 +0000 Received: by mail-pa0-f54.google.com with SMTP id kx10so4955987pab.13 for ; Mon, 08 Jul 2013 18:13:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:message-id:in-reply-to:references:subject:x-mailer :mime-version:content-type:content-transfer-encoding :content-disposition; bh=nouccmuVDZ9HEmQ6LYIiCEacjSuWJJTwXCj3kRoQX0c=; b=YNm2Fo+yDf4dWpzmyv1wikOym5wD02dbgONMv2M3Fi41du54tqUZ6XQDu+bzSoArI6 VMkJceTgMoptwr57Bn3CRkLf1Wi4/KMq/Dmms9WJaYzknP6h5mZs0GGMjQRTT/XfGppV TEdDrTXTSn8o741PLacPR6Mv1H5lt2OXq6ka09I9ar72CH4ljCFc1AqebRXuRYJwkO9y A61CkrIQH/KT2KinHPcojXg8R6ECq5+IrFlgYKukxWMpdLeLo2PLTNTfyaMGW+XJgtAQ 2G6Np/cao9nbpweLdDfdzABHqWm6H0MAXtH2Tq1TbLdaES6rEVmFj0jI3TYQXzzc6kHG gZrw== X-Received: by 10.66.149.66 with SMTP id ty2mr25754250pab.58.1373332422636; Mon, 08 Jul 2013 18:13:42 -0700 (PDT) Received: from [192.168.1.135] ([125.33.124.110]) by mx.google.com with ESMTPSA id mr3sm25024610pbb.27.2013.07.08.18.13.38 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 08 Jul 2013 18:13:39 -0700 (PDT) Date: Tue, 9 Jul 2013 09:13:36 +0800 From: Willem jiang To: dev@cxf.apache.org Message-ID: <459AF87F025E4A7E9557CAAE38BA20F0@gmail.com> In-Reply-To: References: Subject: Re: CXF Client issue when try to handle session for One-Way Operation call X-Mailer: sparrow 1.6.4 (build 1176) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org Please fill a JIRA=5B1=5D and share the patch with us. =5B1=5Dhttps://issues.apache.org/jira/browse/CX=46 -- =20 Willem Jiang Red Hat, Inc. =46useSource is now part of Red Hat Web: http://www.fusesource.com =7C http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) = (English) http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) Twitter: willemjiang =20 Weibo: =E5=A7=9C=E5=AE=81willem On Tuesday, July 9, 2013 at 2:55 AM, Harsha Thirimanna wrote: > Hi , > =20 > I am working for a project that base on web service and client. My issu= e is > in client side. I created the client using CX=46. 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 t= o > the next operation call in same service There may be sequence of operat= ion > 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. But your the expertise of this. Please we want to clear this out.= > This was blocker issue for us really. > =20 > 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 ca= ll , > then this session handle correctly. > =20 > thanks =20