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 9F2294D05 for ; Wed, 25 May 2011 08:51:01 +0000 (UTC) Received: (qmail 39793 invoked by uid 500); 25 May 2011 08:51:00 -0000 Delivered-To: apmail-axis-java-dev-archive@axis.apache.org Received: (qmail 39556 invoked by uid 500); 25 May 2011 08:51:00 -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 39545 invoked by uid 99); 25 May 2011 08:51:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 May 2011 08:51:00 +0000 X-ASF-Spam-Status: No, hits=3.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of kathy.chen23@googlemail.com designates 209.85.161.173 as permitted sender) Received: from [209.85.161.173] (HELO mail-gx0-f173.google.com) (209.85.161.173) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 May 2011 08:50:54 +0000 Received: by gxk26 with SMTP id 26so3564876gxk.32 for ; Wed, 25 May 2011 01:50:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=z7d8+pecLyUSQ2jtHDUWEEwqRDnWMpUy7nFjaGeoF9M=; b=j4Naq+Je/cHMSBROiMfEHct0DI3aRxRd/vmAhYzfQQKTaM78Qv0FUzWDgx9IECkT1U HrpbRimoHchoixPCiJejSB4dkl0aifGPpfOGqAdMu0FtQHVUuT2d24+yhZh6oBQ0stlx lwHjpzaCFEkXmAKZEwqX9UScBUWKA4DmdvmXo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=OAa0qYj10TAxpTbhnRCwyVSvB+sNmVPGb/w/jA1YvXt/K1aaYcjmLIDTWQ7NZOt32s vUSrq0I9F7GFVOc46cr+1KjRNWjAv2P9C3abHkr8CAJKtbY4UGSr/XkfdyqYganhZPIH VacQltDnuNuClvaQghpc7LwiPiKLtsMK/Uq/U= MIME-Version: 1.0 Received: by 10.150.2.2 with SMTP id 2mr4825382ybb.70.1306313433267; Wed, 25 May 2011 01:50:33 -0700 (PDT) Received: by 10.150.191.10 with HTTP; Wed, 25 May 2011 01:50:33 -0700 (PDT) Date: Wed, 25 May 2011 10:50:33 +0200 Message-ID: Subject: addressing in AXIS2 From: Cuiting Chen To: java-dev@axis.apache.org Content-Type: multipart/alternative; boundary=000e0cd4d39a27bdf504a415cc52 X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd4d39a27bdf504a415cc52 Content-Type: text/plain; charset=ISO-8859-1 Hi, there, I am trying to find the way how axis2 know the coming response is for a certain request. Especially in this situation: a user invoke a web service, and this web service need to call another web service to do something, then the first web service will be able to answer the user. So what is the difference between a request is started by a user and by another web service? How do axis2 create a request for a web service to invoke another web service? Does anyone know how axis2 implement this? or which classes are handling such things? Thanks in advance! -- Best regards, Cuiting Chen --000e0cd4d39a27bdf504a415cc52 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi, there,

I am trying to find the way how axis2 know th= e coming response is for a certain request. Especially in this situation: a= user invoke a web service, and this web service need to call another web s= ervice to do something, then the first web service will be able to answer t= he user. So what is the difference between a request is started by a user a= nd by another web service? How do axis2 create a request for a web service = to invoke another web service?

Does anyone know how axis2 implement this? or which cla= sses are handling such things? Thanks in advance!

-- <= br>Best regards,
Cuiting Chen

--000e0cd4d39a27bdf504a415cc52--