Ian, yes, it's confusing....in this case "Messaging" implies someone who creates a complete SOAP message by hand. So, follow the pattern in DynamicInvoker and you should be safe :)
-- dims On Fri, 05 Nov 2004 23:25:51 +0000, Ian Dickinson <[EMAIL PROTECTED]> wrote: > [I'm resending this message as it hasn't appeared on the list after some > hours. Apologies if any gets this twice. -ian] > > > > > From: Davanum Srinivas [mailto:[EMAIL PROTECTED] > > look into samples\client package specifically the > > DynamicInvoker.java for an example > Thanks, that's helpful. It's bascially equivalent to what I've been > doing, which is reassuring. I notice, though, that the array of params > you pass to Call.invoke() in the sample is just the deserialised values > from the command line arguments. Does that suggest that the Javadoc > comment on Call.invoke() that I quoted is no longer relevant? > > > > """ > > > Invokes the operation associated with this Call object using the > > > passed in parameters as the arguments to the method. For Messaging > > > (ie. > > > non-RPC) the params argument should be an array of SOAPBodyElements. > > > *All* of them need to be SOAPBodyElements, if any of them > > > are not this > > > method will default back to RPC. In the Messaging case the > > > return value > > > will be a vector of SOAPBodyElements. > > > """ > > Thanks, > Ian > > _____________________________________________________________________ > Ian Dickinson HP Labs, Bristol, UK mailto:[EMAIL PROTECTED] > net www.hpl.hp.com/personal/Ian_Dickinson ph +44 (117) 312 8796 > > -- Davanum Srinivas - http://webservices.apache.org/~dims/
