On Thu, 1 Sep 2005, Chris Nappin wrote: > > > I think in document/literal document types are supposed to map > one-to-one > with messages so a service can infer the operation from the > document type. > > Many web service toolkits (.Net, JWSDP, etc) appear to use this > convention, although I've never seen it formally defined in a standard > anywhere.
You mean the "wrapped" style, presumably, where there's a convention that the document element matches the operation name in the WSDL. Yes, that's a Microsoft idea and normal in .NET. (Note to SOAP beginners: AFAIK, "wrapped" isn't a keyword in the WSDL vocabulary; wrapped services are doc-lit with a particular naming convention.) > In my experience Axis only needs this if you have more than one > operation in a single doc/literal service. If you only have one > operation then it isn't fussy (unlike JWSDP, for example). Agreed. However, I had in mind an intermediate case. Suppose you have a service with multiple operations in doc-lit style-usage. I think you are then required to make each operation take and/or return a different type of document s.t. the operations can be distinguished. As long as documents map uniquely to and from operations, it doesn't matter whether the document type is named after the operation. I don't know how Axis copes with that. Guy Rixon [EMAIL PROTECTED] Institute of Astronomy Tel: +44-1223-337542 Madingley Road, Cambridge, UK, CB3 0HA Fax: +44-1223-337523
