Return-Path: X-Original-To: apmail-axis-java-dev-archive@www.apache.org Delivered-To: apmail-axis-java-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 8FCC77DA3 for ; Fri, 5 Aug 2011 12:59:04 +0000 (UTC) Received: (qmail 98089 invoked by uid 500); 5 Aug 2011 12:59:03 -0000 Delivered-To: apmail-axis-java-dev-archive@axis.apache.org Received: (qmail 97667 invoked by uid 500); 5 Aug 2011 12:59:02 -0000 Mailing-List: contact java-dev-help@axis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-dev@axis.apache.org Delivered-To: mailing list java-dev@axis.apache.org Received: (qmail 97652 invoked by uid 99); 5 Aug 2011 12:59:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Aug 2011 12:59:01 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of deepalk@gmail.com designates 209.85.161.45 as permitted sender) Received: from [209.85.161.45] (HELO mail-fx0-f45.google.com) (209.85.161.45) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Aug 2011 12:58:55 +0000 Received: by fxbb27 with SMTP id b27so1452451fxb.32 for ; Fri, 05 Aug 2011 05:58:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=Eefc+SYXedHksbYi6XPyURQwMYBVX1k86vs+MdxphU8=; b=jOVQATmyHTO2b4f3roOin9WOdL+kLA/BxVPGRF9SP1ltTVNUMtaJiCJtoD2uJVTpEu BsJ+vlea8Kuzy+b7SbPI+DPfglOYDGAB8GcY1SsU54di8kzdNEbAVGjRCjTsRJT9JAvN Zl7981HuMX51a4Qp+FYClNQijmMT3q1cnFM+E= MIME-Version: 1.0 Received: by 10.204.50.130 with SMTP id z2mr186611bkf.0.1312549113051; Fri, 05 Aug 2011 05:58:33 -0700 (PDT) Received: by 10.204.14.7 with HTTP; Fri, 5 Aug 2011 05:58:33 -0700 (PDT) In-Reply-To: References: <4E39EB21.3070800@gmail.com> <4E3A85BD.5080207@opensource.lk> <4E3BD953.9070504@gmail.com> Date: Fri, 5 Aug 2011 08:58:33 -0400 Message-ID: Subject: Re: Non blocking with two channel is broken From: Deepal Jayasinghe To: java-dev@axis.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Amila, You might not remember the two transport functionality since this was done a long time ago, and in fact those days you were contributing the ADB and code generation. Actually, the long running services idea was initially developed based on the two transport semantics. The correct way to handle two transport or any request with replyTo (not anonymous), is to send the ACK on the request transport and send the reply through the reply to address. So, we had this feature and I have used and demoed this feature a number of times in various conferences. I sent this email to mailing list to see whether someone has removed the source code as part of some discussion, because I am sure I have missed some long discussion after 2008. Now, it is sure that this feature was not removed intentionally. So I will fix it correctly. With my academic work I hardly find time to go through the mailing list and try to respond as much as I can. So going through commit messages is not a practical solution for me (though I spent two hours doing that). In fact I am not actively looking at Axis2 code base since 2008, so it is hard for me to navigate all those changes. Thanks all of you for the actively participation, I will implement this feature correctly (of course when I find a free time). Thanks, Deepal On Fri, Aug 5, 2011 at 8:25 AM, Amila Suriarachchi wrote: > > > On Fri, Aug 5, 2011 at 5:21 PM, Deepal jayasinghe wro= te: >> >> >> >> On Thu, Aug 4, 2011 at 7:32 PM, Deepal Jayasinghe >> wrote: >>> >>> >> >>> >> I looked and the code segment you mentioned, but that is to process >>> >> long >>> >> running services. We had somewhat similar code to process request >>> >> comes with >>> >> replyTo header. If no one has removed then, we can fix the issue in >>> >> AMR. >>> > >>> > This is for processing addressing headers with replyTo header. >>> I agree, but that is inside isAsync, so we need to have the parameter >>> to come to this logic. >> >> yes you need to add this parameter DO_ASYNC =3D "messageReceiver. >> invokeOnSeparateThread"=A0 to services.xml. >> >> Do you want to make this by default. Then what about the backward >> compatibility :) >> >> Long running services and two transports non-blocking invocations are tw= o >> different things. So, we do not need to make DO_ASYN the default. Howeve= r, I >> am talking about the removal of an existing functionalities, so backward >> compatibility is already broken. > > I am not sure about the functionality you talk about. Is it possible you = to > find the commit which has removed that functionality you talk about? > > thanks, > Amila. > >> >> Thanks., >> Deepal > > > > -- > Amila Suriarachchi > WSO2 Inc. > blog: http://amilachinthaka.blogspot.com/ > --=20 http://blogs.deepal.org --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org For additional commands, e-mail: java-dev-help@axis.apache.org