> Hi Bruno,

> In theory (given it's the goal of Web services), the fact it's a .NET
> service should make no difference.  The difference between SCA and the
> SoapClient (I don't know SCO) will largely come down to how you work
> with the complexTypes.  With the SoapClient (If I remember correctly),
> you will use DOM to create a complex type and can use SimpleXML to
> read any complex type which is returned.  With SCA you use SDO to
> create and read complex types.

> An <any />, which you mentioned in your previous post, is a bit of a
> pain to work with.  With SDO, this will result in what is called an
> "Open Type" (a type which can take any content).  You will need an XSD
> for the content you will put in place of the any (I would assume
> the .NET service defines a schema for what can go in place of the
> any).  You can then use SDO to create a DataObject for that content,
> fill it in and then pass it in the request to the Web service.

> Note, I've never needed to work with open types in an SCA client, so
> there may be some devils in the details...

> For information on open types, see example 4 in the SDO docs:
> http://php.net/manual/en/sdo-das-xml.examples.php

> I hope this helps.

> Regards, Graham.

> On 5 Aug, 22:13, "Bruno Reis" <bruno.p.r...@gmail.com> wrote:
> > Hi there.

> > Can someone please send me an example of how to send a complex type to a
> > .net service?
> > I´m having no sucess at this.
> > How is the xml supposed to be?
> > How do I do it using SCO or SoapClient?

> > Thanks,
> > Bruno