I'm advocating:
Determine requirements.
Write database if needed and create business logic.
All done.
There is no thinking about how WSDL or XML is presented because the .Net web services generate WSDL/XML on the fly at runtime.
Writing WSDL and XML by hand is definitely a hammer and chisel approach and was probably required in the early web services days, but not today.
Tell me if I'm missing something obvious, but I have been writing web services in .Net for several years without ever having to deal directly with XML.
Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site:
http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
-----Original Message-----
message: 3
date: Fri, 8 Oct 2010 17:45:14 -0400
from: TAllen@xxxxxxxxxxxx
subject: Re: [WEB400] Microsoft .NET frontending IBM i
Huh? You are advocating the code first approach? That's like writing a bunch of programs and then designing a database to fit what you wrote.
Thanks,
Todd Allen
EDPS
Electronic Data Processing Services
tallen@xxxxxxxxxxxx
As an Amazon Associate we earn from qualifying purchases.