Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 13390 invoked from network); 30 Sep 2005 11:15:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 30 Sep 2005 11:15:59 -0000 Received: (qmail 71685 invoked by uid 500); 30 Sep 2005 11:15:58 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 71099 invoked by uid 500); 30 Sep 2005 11:15:56 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 71088 invoked by uid 99); 30 Sep 2005 11:15:56 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Sep 2005 04:15:56 -0700 X-ASF-Spam-Status: No, hits=1.9 required=10.0 tests=RCVD_BY_IP,RCVD_IN_BL_SPAMCOP_NET,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of ruchith.fernando@gmail.com designates 72.14.204.207 as permitted sender) Received: from [72.14.204.207] (HELO qproxy.gmail.com) (72.14.204.207) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Sep 2005 04:16:02 -0700 Received: by qproxy.gmail.com with SMTP id o12so63832qba for ; Fri, 30 Sep 2005 04:15:34 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=awMvFdq5NKorAAcHAGtd8+/CIy0e5buEp4MfJhBr3amtSIC5jiAqLzwZhjOzefdx7bKMWB45k/ULlY5r7W2222tPiu/M5k2kpRSNNtD25qyaXBJZkfBGcIr/r52SBjBU0Qag5lqwyS5mdC9AMXp7Iq1S1hvX85OEyw9TYgUaAjI= Received: by 10.64.241.5 with SMTP id o5mr892905qbh; Fri, 30 Sep 2005 04:15:34 -0700 (PDT) Received: by 10.64.201.4 with HTTP; Fri, 30 Sep 2005 04:15:34 -0700 (PDT) Message-ID: <559c463d0509300415i6f8f036fxcf3ca2a0219a1080@mail.gmail.com> Date: Fri, 30 Sep 2005 17:15:34 +0600 From: Ruchith Fernando Reply-To: Ruchith Fernando To: vikas kumar Subject: Re: [AXIS2] Module in the chains?? Cc: axis-dev@ws.apache.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <559c463d050929043141c83a7e@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi, Please see my comments below: On 9/29/05, vikas kumar wrote: > Thanks ruchit for the comments.. > But i have a few more doubts.. > There is only one instance of the handler and module implementaion classe= s, > is there only one instance of the chain too?? Yes there's only one instance > If the above case is true : Is'nt it a bottleneck?? > Does an incoming request have to wait for the request ahead of it to get > processed... > If no?? who does the threading?? No The sevlet container does the threading. For example there will be multiple threads created for each of the requests (depending on the servlet container). As long as there are no synchronized blocks within the handler code there will not be any bottlenecks. > > Pardon me if i am being too inquisitive.. No problem :-). Please feel free to ask any question related to Axis2. > Thanks for ur patience! > > > > On 9/29/05, Ruchith Fernando wrote: > > Hi, > > > > Please see my comments below: > > > > On 9/29/05, vikas kumar < pvikasroonwal@gmail.com> wrote: > > > Hi all! > > > I have various services running in axis2 and have a few modules engag= ed > to > > > these services in different combination. > > > If i understand the concept correctly.. these modules are present in = the > all > > > flow chains but are active only if engaged for a particular service. > > > > When Axis starts up all the available modules will be loaded. But only > > those, that are engaged via the axis2.xml (E.g.: using > ref=3D"foo"/>) will be engaged globally. Also if the available modules > > can be engaged per service by having the in the > > services.xml file of that particular service. > > > > When Axis2 is used with a servlet container such as Apache Tomcat we > > can use the Web Admin tool to engage modules for a certain service or > > globally. > > > > When a module is engaged, the handlers of that module will be > > available in the flows that they are defined to be placed. This is > > done using the and elements in the module.xml file. > > Therefore 'modules' are not present in the flows but the handlers that > > are defined to be in a certain flow and in a certain phase are active > > only when they are engaged. > > > > > > > > So, does axis2, fork separate instances of the module/handler classes > for > > > every service to which they are engaged or do all the service flow > chains > > > use the same instance created when these module/handler classes are > loaded > > > by the axis engine? > > > > Axis2 will create an instance of each of the handlers and the module > > implementation class (if available) defined in the module.xml and > > those same instances will be used. Please note that if the same > > handler class is used in two modules that are engaged there will be > > two instances of that handler. > > > > > > > > Can someone direct me to the relevant pieces of codes and the way thi= ngs > are > > > done.. > > > > > > All the help is appreciated! > > > Thanks in advance! > > > Have a nice day! > > > > > > > > > -- > > Ruchith > > > > Thanks, -- Ruchith