Cory wrote:
> I'm curious as to what the under-pinnings of a message style service are?
Do you mean the code inside the method that ultimately gets called? I'm currently planning to use JDOM to work directly with the XML.
> When the service is described via wsdl, surely it's doc/lit?
> Else I could be handed an envelope whose contents can't be
> validated against a given schema.
My current lifeline is the Axis User Guide. So I understand "Document" and "Wrapped" as these two method signatures:
public void method(PurchaseOrder po)
public void purchaseOrder(String item, int quantity, String description)
But I'm still trying to understand what "document/literal" means. Sorry! I do intend for there to be a schema that describes what is allowed/required in the body of the SOAP message.
> The default microsoft implementation is a "wrapped" doc/literal service (I believe).
> You have little to worry about if your folk are only *consuming*,
> it's just that if you're developing web services on the ms platform,
> by default, you get a "wrapped" style of service in order to emulate RPC.
Still confused, but it's sounding like as long as I stay away from java:RPC, I can deal with the body of the message however I please. They just need to send the body as
<purchaseOrder>
<item>123</item>
</purchaseOrder>
And they won't know or care that I use "Document" "Wrapped" or "Message" on the Axis side. Does that sound right?
--
Wendy Smoak
Applications Systems Analyst, Sr.
Arizona State University, PA, IRM
