Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Axis2] Changed Call method?
Date: Thu, 19 May 2005 17:29:01 +0530
Message-ID: <E0467379DD4FA84BAF6E42D3161A9A08B158EC@inhyms21.ca.com>
Thread-Topic: [Axis2] Changed Call method?
Thread-Index: AcVcXZR+J/dNEZx3QQS7nDao5byXEwACmh8g
From: "Shahi, Ashutosh" <Ashutosh.Shahi@ca.com>
To: <axis-dev@ws.apache.org>,
	"Srinath Perera" <hemapani@gmail.com>

Srinath,
       Looking to confirm what u said,I noticed following code in
InvokeBlocking() method:
        if (isEnvelope) {
            return resEnvelope;
        } else {
            return resEnvelope.getBody().getFirstElement();
        }
And in prepareTheSystem() method:
        if (toSend instanceof SOAPEnvelope) {
            envelope =3D (SOAPEnvelope) toSend;
            isEnvelope =3D true;
        } else {
            SOAPFactory omfac =3D OMAbstractFactory.getSOAP11Factory();
            envelope =3D omfac.getDefaultEnvelope();
            envelope.getBody().addChild(toSend);
            isEnvelope =3D false;
        }


This tells we can pass SOAPEnvelope and I think, if we send Envelope
we'll receive envelope, so casting should be safe. So the Envelope
structure u said should not be possible. Am I missing something?

Also, I guess one should be allowed to pass complete envelope, else how
can a user add soap header elements? Also, SAAJ connection classes
require envelopes passing capability, so if this doesn't happen in OM
I'll have to do some extra coding there.

Ashutosh

-----Original Message-----
From: Srinath Perera [mailto:hemapani@gmail.com]=20
Sent: Thursday, May 19, 2005 3:30 PM
To: axis-dev@ws.apache.org
Subject: Re: [Axis2] Changed Call method?

>             Is it that we have sendReceiveSync() method in
> org.apache.axis.clientapi.Call replaced by:=20
>=20
> public OMElement invokeBlocking(String axisop, OMElement toSend)?=20
Yes

> This method takes an additional parameter axisop. What all values can
it
> take and why has this been added?=20
> I see a sample program passing "echo" to it, is there any predefined
list
> from which these values are taken?=20
It is the name of the Operation you want call in the ServiceEndpoint
.. echo is the name of the operation !

 =20
> Also, the return type has been changed to OMElement from SOAPEnvelope,
if I
> pass a SOAPEnvelope, can I assume the response will be SOAPEnvelope as
well
> and typecast safely?=20

No the return type is a OMElment .. if u pass SOAPEnvelope it would be

<SOAPEnvelope ...>
<body>
    <SOAPEnvelope> ....</SOAPEnvelope>
</body>
 that goes on the wire !!

Thanks
Srinath