True, they are all XML, but I want to avoid having to get clients to need to reformat XML in order to send it to my web service.
The least amount of time is probably a good indication! I'm planning on using XSDs, so an XmlElement does make sense. I can always use the XSD to generate a typed dataset later, if that makes things easier for coding. Thanks, Erick > -----Original Message----- > From: Unmoderated discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of Marsh, Drew > Sent: Monday, September 20, 2004 5:36 PM > To: [EMAIL PROTECTED] > Subject: Re: [ADVANCED-DOTNET] Method for web service method > parameters > > Erick Thompson wrote: > > What is the best/recommended way to pass schema bound objects when > > using web services? For example, say I have an ordering system that > > accepts a customer and an order. I have a customer XSD that defines > > the what data the customer object can hold. Now, I have a > web service > > with a method called AddCustomer (for example). I see a number of > > different ways that the customer data can be passed in.=20 > > > > ... code snipped for brevity ... > > > > My question is, what is going to be the best/most flexible > in terms of > > versioning, cross platform compatibility, maintenance, etc? My gut > > feeling is that the XmlDoucment is the best, but I want to > check with > > people before moving ahead with it. > > Erik, > > IMVHO, the truth is none of those signatures matters up > front. Why? Because it's simply an implementation detail. > What's most important is that you design the schemas and WSDL > first, in a "pure" XML WS-Standards compliant way. Then, you > leverage the toolset that something like .NET provides you to > implement it. You can always swap the implementation out with > something more effective without ever affecting the client > because all they every care about is sending you SOAP > messages with XML documents that match a schema that you have defined. > > XmlElement is going to provide you the most flexibility, but > you're web method's logic is gonna be more verbose and > complex. If you instead use a DataSet or class generated by > XSD exe, it's gonna handle the parsing for you, but may run > into limitations depending on the complexity of your schema. > > All that said, my vote goes for whatever gets the job done in > the least amount of time. :) > > Cheers, > Drew > > =================================== > This list is hosted by DevelopMentor(r) http://www.develop.com > Some .NET courses you may be interested in: > > Essential .NET: building applications and components with > CSharp August 30 - September 3, in Los Angeles > http://www.develop.com/courses/edotnet > > View archives and manage your subscription(s) at > http://discuss.develop.com > =================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in: Essential .NET: building applications and components with CSharp August 30 - September 3, in Los Angeles http://www.develop.com/courses/edotnet View archives and manage your subscription(s) at http://discuss.develop.com
