More dummy questions: 1) So, three cases of interest: rpc/lit, doc/lit unwrapped, doc/lit wrapped. For the latter two, the elements are as named by the element names in the parts, not by the part names themselves, as in the rpc/lit case.
2) Where do we store the style? I'm digging down through ServiceInfo->InterfaceInfo->OperationInfo, and I seem to be somehow missing it .. hang on, it's in AbstractServiceConfiguration, and those live in the service factory bean. I don't see a path from the model (ServiceInfo, etc) to the service factory bean. Should the factory scribble the style information into the service itself somewhere? > -----Original Message----- > From: Daniel Kulp [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 01, 2007 2:53 PM > To: Benson Margulies > Cc: [email protected] > Subject: Re: MessagePartInfo > > On Thursday 01 November 2007, Benson Margulies wrote: > > When is a part an element and when is a part a type? Or, more > > concretely, what goes on the wire in the later case? > > In the rpc/lit case, parts should be types. In the doc/lit case, parts > should be elements. > > In the rpc/lit case where they are types, on the wire, it should be: > > <ns1:opname xmlns:ns1="namespace_from_soap_operation"> > <partname1>....</partname1> > <partname2>....</partname2> > </ns1:opname> > > The elements that form the on-the-wire form for the parts are > unqualified. > > -- > J. Daniel Kulp > Principal Engineer > IONA > P: 781-902-8727 C: 508-380-7194 > [EMAIL PROTECTED] > http://www.dankulp.com/blog
