A Dataset type includes its own schema, and it includes a bunch of additional proprietary fields that ADO.NET uses for transaction and session control. In order to consume the element, you need to process the embedded schema on the fly, and in order to maintain transactional integrity, you need to make sure that you set the appropriate proprietary fields properly.
If you want to enable interoperability, you should convert the Dataset to an array and expose it as a predefined type.
Anne
Could you tell me why ?
De : Anne Thomas Manes [mailto:[EMAIL PROTECTED]]
Envoyé : 23 janvier 2006 18:03
À : [email protected]
Objet : Re: .NET complex type ...
Don't use Dataset types.
On 1/23/06, Rémi Guilbert < [EMAIL PROTECTED]> wrote:
Hi, I made a Test class to consume .Net complex types like Object array, Dataset and TypeDataSet. I doesn't have problem with Object array, but I don't understand how manipulate the Objects generate by Axis 1.3 for DataSet and TypeDataSet object return. I put my Test class in attachment and the WSDL is located at http://www.radiopointnet.com/ws/mainservice.asmx?WSDL
I need your help …
Best Regards,
Remi
Rémi Guilbert
Analyste, Division des systèmes, Support aux développeurs
Service d'informatique et des télécommunications
Pavillon Louis-Jacques-Casault, local 2454
Université Laval, Québec, Canada, G1K 7P4
Téléphone / Phone number : 1-418-656-2131 ext. 14692
Télécopieur / Fax number : 1-418-656-7305
Avis relatif à la confidentialité / Notice of Confidentiality / Advertencia de confidencialidad < http://www.rec.ulaval.ca/lce/securite/confidentialite.htm>
