Return-Path: 
 <axis-dev-return-38532-apmail-ws-axis-dev-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-dev-archive@www.apache.org
Received: (qmail 99134 invoked from network); 30 Aug 2005 23:03:54 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 30 Aug 2005 23:03:54 -0000
Received: (qmail 20155 invoked by uid 500); 30 Aug 2005 23:03:51 -0000
Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org
Received: (qmail 20137 invoked by uid 500); 30 Aug 2005 23:03:51 -0000
Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
list-help: <mailto:axis-dev-help@ws.apache.org>
list-unsubscribe: <mailto:axis-dev-unsubscribe@ws.apache.org>
List-Post: <mailto:axis-dev@ws.apache.org>
List-Id: <axis-dev.ws.apache.org>
Delivered-To: mailing list axis-dev@ws.apache.org
Received: (qmail 20119 invoked by uid 99); 30 Aug 2005 23:03:51 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Aug 2005 16:03:51 -0700
X-ASF-Spam-Status: No, hits=0.5 required=10.0
	tests=HTML_20_30,HTML_MESSAGE,RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: domain of csethil@gmail.com designates
 64.233.184.203 as permitted sender)
Received: from [64.233.184.203] (HELO wproxy.gmail.com) (64.233.184.203)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Aug 2005 16:04:05 -0700
Received: by wproxy.gmail.com with SMTP id 69so3072wri
        for <axis-dev@ws.apache.org>; Tue, 30 Aug 2005 16:03:48 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:mime-version:content-type;
        b=m2d79JWH+IObxWcEX0KYmH8M2gE6crbRF2MNcPC6Ak54WnTB1H1ea1rKo295DVvljLo2tV6vrRgLnUqwkJ2RUMpIMRl1nQv1pL4C4cYcOh6k5nAAWgfUdvB4o4he7CTgbfmEkIpjnwxlI/ae/uaRFI7FomzJy/Y6DqOO7Jxojyo=
Received: by 10.54.81.10 with SMTP id e10mr248298wrb;
        Tue, 30 Aug 2005 16:03:48 -0700 (PDT)
Received: by 10.54.11.31 with HTTP; Tue, 30 Aug 2005 16:03:48 -0700 (PDT)
Message-ID: <e9115cfd050830160332a79a8d@mail.gmail.com>
Date: Wed, 31 Aug 2005 05:03:48 +0600
From: Thilina Gunarathne <csethil@gmail.com>
To: axis-dev@ws.apache.org
Subject: [Axis2] Clarifications needed for Local transport Receiver &
 RawXMLInOnlyMessageReceiver
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_1097_21267332.1125443028779"
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

------=_Part_1097_21267332.1125443028779
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi all,
Can somebody pls clarify me the possible usage of Local Transport=20
Receiver... I found that it has not undergone many improvements we did to=
=20
other parts lately. eg : MTOM will not work there. REST is not=20
there.etc.......
 Also I found that the implementer of the service (Skeleton) should provide=
=20
a return type when writing InOnly operations using=20
RawXMLInOnlyMessageReceiver. This InOnly Message Receiver takes takes the=
=20
response of the service impl method to a OMElement, but does not do anythin=
g=20
as I can see..Following is the piece of code from the MessageReceiver. Is=
=20
this the expected behavior... If so what is the usage of that......

// invoke the WebService

OMElement result =3D (OMElement) method.invoke(obj, parms);

Thanks & Regards,
~Thilina

---------------------------------------------------------------------------=
-------------------------------------------------

"May the SourcE be with u"=20
http://www.bloglines.com/blog/thilina=20
http://webservices.apache.org/~thilina/

------=_Part_1097_21267332.1125443028779
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<div>Hi all,</div>
<div>Can somebody pls clarify me the possible usage of Local Transport Rece=
iver... I found that it has not undergone many improvements we did to other=
 parts lately. eg : MTOM will not work there. REST is not there.etc......
.</div>
<div>&nbsp;</div>
<div>Also I found that the implementer of the service (Skeleton) &nbsp;shou=
ld provide a return type when&nbsp;writing InOnly operations using&nbsp; Ra=
wXMLInOnlyMessageReceiver. This InOnly Message Receiver takes takes the res=
ponse of the service impl method to a OMElement, but does not do anything a=
s I can see..Following is the piece of code from the MessageReceiver. Is th=
is the expected behavior... If so what is the usage&nbsp;of that......
</div><font size=3D"2">
<blockquote dir=3D"ltr" style=3D"MARGIN-RIGHT: 0px">
<p>// invoke the WebService</p>
<p>OMElement result =3D (OMElement) method.invoke(obj, parms);</p></blockqu=
ote>
<div></div></font>Thanks &amp; Regards,
<div>~Thilina<br clear=3D"all"><br>----------------------------------------=
---------------------------------------------------------------------------=
--------- <br>&quot;May the SourcE be with u&quot; <br><a href=3D"http://ww=
w.bloglines.com/blog/thilina">
http://www.bloglines.com/blog/thilina</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href=3D"http://webserv=
ices.apache.org/~thilina/">http://webservices.apache.org/~thilina/</a> </di=
v>

------=_Part_1097_21267332.1125443028779--