Re: property PROP_SEND_XSI

[BOURLON Agnès]

Dennis,

I don't know if it 's that you need ... but this is a sample that our client
generate :
The only complex type specified the "first" object and in this object, the
only xsi specified parameters are the arrays (Foo[])
..
<soapenv:Body>

  <ns1:myMethod
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
xmlns:ns1="urn:MyService ">

   <in0 xsi:type="ns2:MyRequest" xmlns:ns2="http://myservice.com";>

    <isOk>false</isOk>

    <timeSlot>

     <date>

      <iso8601>2002-12-15T17:00+01:00</iso8601>

     </date>

    </timeSlot>

    <information>

     <label>This is the information</label>

     <description>xxxx</description>

    </information>

    <fooList soapenc:arrayType="ns2:Foo[2]"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";>

     <item>

      <a1>17</aA>

      <a2>

       <b>String</b>

      </a2>

     </item>

     <item>

      <a1>18</aA>

      <a2>

       <b>String</b>

      </a2>

     </item>

    </ fooList >

   </in0>

  </ns1:myMethod>

 </soapenv:Body>

..


----- Original Message -----
From: "Dennis Sosnoski" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, December 19, 2002 11:39 AM
Subject: Re: property PROP_SEND_XSI


> BOURLON Agnès wrote:
>
> >Do you know if it can work (no xsi type) with GLUE Server or Apache SOAP
> >Server?
> >
> I haven't tried eliminating xsi type with either of those, but from what
> I've seen I think GLUE supports untyped RPC but Apache SOAP does not.
> Perhaps someone with more experience on these two can comment and
> correct me if I'm wrong.
>
> >And a last question.. if we set the PROP_SEND_XSI to false in our Axis
> >Client (that we use to test our service in Axis server) we noticed that
some
> >types in the envelope can contain the xsi types ....
> >For example in the case of the Array  type ..is it for fix the size
during
> >the deserialization?
> >
> As I read the SOAP 1.1 spec the Array type is required, though it can be
> a generic 'SOAP-ENC:arrayType="xsd:ur-type[4]', for instance. When this
> form is used the individual elements all need to give type information.
>  From looking at the code I think Axis may put a stronger restriction on
> what can be sent, requiring that the type of the array elements be a
> specific serializable type. Either way some type information is going to
> be required for arrays. I don't know where else you've seen the types,
> if you have specific examples let me know.
>
> Having the types included should never be harmful as far as I know.
>
>   - Dennis

___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com