On 5/23/05, Shahi, Ashutosh <[EMAIL PROTECTED]> wrote: > > Guys, > Any words on this? I would personally prefer the ability to send/receive > SOAPEnvelope as well along with the existing capability to send/receive > OMElement. I am not dead agienst the giving both. Yet seems we can live with only OMElement too. The decission is up to the community > > Also, Srinath isn't it that if we are sending a SOAPEnvelope we should > know the operation name from it irrespective of the style/use? No if the style is doclit (unwrapped) Thanks Srinath > -----Original Message----- > From: Srinath Perera [mailto:[EMAIL PROTECTED] > Sent: Thursday, May 19, 2005 5:50 PM > To: [email protected] > Cc: Shahi, Ashutosh > Subject: Re: [Axis2] Changed Call method? > > 1) The Code is changed now .. the current code supports the OMElement > only > To change the things OMElement vs SOAPEnvelope .. I am nutral on the > case. > I let the developer community decide what is better > Guys .. thoughts? > > 2) you know the operation name from OMElement If and only if the style > is rpc/ doc-literl-wrapped, so the argument not hold all the time > > > > On 5/19/05, Shahi, Ashutosh <[EMAIL PROTECTED]> wrote: > > Also, Why do we need to add the name of the method when it is already > > contained in OMElement or SOAPEnvelope? > > > > Ashutosh > > > > > > -----Original Message----- > > From: Shahi, Ashutosh > > Sent: Thursday, May 19, 2005 5:30 PM > > To: '[email protected]'; 'Srinath Perera' > > Subject: RE: [Axis2] Changed Call method? > > > > 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 = (SOAPEnvelope) toSend; > > isEnvelope = true; > > } else { > > SOAPFactory omfac = OMAbstractFactory.getSOAP11Factory(); > > envelope = omfac.getDefaultEnvelope(); > > envelope.getBody().addChild(toSend); > > isEnvelope = 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:[EMAIL PROTECTED] > > Sent: Thursday, May 19, 2005 3:30 PM > > To: [email protected] > > Subject: Re: [Axis2] Changed Call method? > > > > > Is it that we have sendReceiveSync() method in > > > org.apache.axis.clientapi.Call replaced by: > > > > > > public OMElement invokeBlocking(String axisop, OMElement toSend)? > > Yes > > > > > This method takes an additional parameter axisop. What all values > can > > it > > > take and why has this been added? > > > I see a sample program passing "echo" to it, is there any predefined > > list > > > from which these values are taken? > > It is the name of the Operation you want call in the ServiceEndpoint > > .. echo is the name of the operation ! > > > > > > > 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? > > > > 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 > > > > > >
