On Jan 3, 2008 10:52 PM, Glen Daniels <[EMAIL PROTECTED]> wrote: > Hi Anne, all: > > Anne Thomas Manes wrote: > > SOAP encoding is much more likely to be used in a code-first scenario, > > but you must make sure that it also works in a WSDL-first scenario. > > +1 > > > Regarding one of your questions, you would never see an element > > defined as follows: > > > > <s:element name="TestSoapElement2"> > >> <s:complexType> > >> <s:sequence> > >> <s:element name="param1" type="s:string"/> > >> <s:element name="param2" type="soapenc:Array"/> > >> </s:sequence> > >> </s:complexType> > >> </s:element> > > > > First off, you would define a named complexType rather than an > > element. And second, you never define an element simply as > > soapenc:Array. The ComplexType would look something like this: > > If this isn't a top-level element (i.e. if this is an element referenced > inside an outermost complexType) it's certainly ok - but your point is > well taken. For RPC style you must use the "type" attribute in WSDL 1.1 > <part> definitions, not the "element" attribute. > > As for soapenc:Array - it's not out-of-spec to use it directly, and we > support this in Axis1. It becomes an Object[].
So you basically telling <s:element name="TestSoapElement2"> >> <s:complexType> >> <s:sequence> >> <s:element name="param1" type="s:string"/> >> <s:element name="param2" type="soapenc:Array"/> >> </s:sequence> >> </s:complexType> >> </s:element> use Object[] as the type of the param2 isn't it? even in this case people people can not use int, double and they have to use Integer Double etc.. In this case how we going to extend this to support double arrays? What I thought to add soapencoding.Array object as a child object and handle this in serializing logic. I agree that in the model I have done it is not much user friendly. But we can extend that to support any thing and people can do any thing with it. Sometimes this may be important than getting a user friendly interface with a limited functionality (Anyway it is my personal preference). But if we don't going to think about this I am ok to change this to Object[] assuming only one dimensional arrays being used. Amila. > > In general, Amila, SOAP array types want to turn into language arrays, > not MyCustomArrayClass, just like SOAP doubles want to turn into > Doubles/doubles (depending on nillable), not MyDoubleClass. > > --Glen > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Amila Suriarachchi, WSO2 Inc.
