In your first case, that would seem to imply a Message style operation, not Document. In the second case, that would seem to imply "bad" design. :-)
-----Original Message----- From: Vidyanand Murunikkara [mailto:[EMAIL PROTECTED]] Sent: Friday, November 22, 2002 3:33 PM To: [EMAIL PROTECTED] Subject: RE: Style=document over RPC ? I am not an expert either. But the soap:body could be a set of document fragments and not neccesarily a single document. check this http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwebsr v/html/wsdlexplained.asp. Correct me if I am wrong. And also what if there is more than one method in the same service which takes in the same type as the input ? Thanks Vidyanand. -----Original Message----- From: Douglas Bitting [mailto:[EMAIL PROTECTED]] Sent: Friday, November 22, 2002 3:25 PM To: '[EMAIL PROTECTED]' Subject: RE: Style=document over RPC ? As near as I can tell, document based operations are discovered based on the type of the parameter. That is, if a <PurchaseOrder> comes in, and <PurchaseOrder> is mapped to foo.PurchaseOrder, the method that is invokes is that which has the single argument of type foo.PurchaseOrder. Seems like a perfectly valid approach since the document is supposed to define the operation. Of course, if my understanding of how this works is wrong... feel free to correct me. :-) Cheers, --Doug -----Original Message----- From: Vidyanand Murunikkara [mailto:[EMAIL PROTECTED]] Sent: Friday, November 22, 2002 3:17 PM To: [EMAIL PROTECTED] Subject: Style=document over RPC ? Hi folks There has been some heated discussions in axis-user over rpc style or document style recently which basically started off with someone asking if they could use a WSDL with document style and the Axis server would use RPCProvider to do all the XML <-> Java Binding. So for anyone outside it is a document based operation but at the server side the RPC provider will be used to call the corresponding method after doing all the required XML-> Java conversions. The user need not worry about any of the marshalling/unmarshalling. Now comes the question as to how we identify the operation from the incoming message. We could use soapactionURI to indicate which operation needs to be called. We have made a slight modification to the code to make this work... and it seems to work in most "Normal" cases. Do you think such a feature need to be added to Axis ? Thanks Vidyanand.
