I agree, and if you end up with an ugly WSDL, it's probably because you have ugly code.
________________________________________
From: web400-bounces@xxxxxxxxxxxx [web400-bounces@xxxxxxxxxxxx] On Behalf Of Richard Schoen [richard@xxxxxxxxxxxxxxx]
Sent: Friday, October 08, 2010 5:28 PM
To: web400@xxxxxxxxxxxx
Subject: Re: [WEB400] Microsoft .NET frontending IBM i
Ugh right back. That sounds much more Hammer and Chisel-ish. Clang, Clang :-)
Why not write business logic first and auto-generate WSDL on the fly ?
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
------------------------------
message: 6
date: Fri, 8 Oct 2010 17:08:12 -0400
from: TAllen@xxxxxxxxxxxx
subject: Re: [WEB400] Microsoft .NET frontending IBM i
Generated WSDL and XML?
That sounds like the code first approach. Ugh. Always use the contract
first approach where you create the WDL and schemas and generate the code
stubs from that.
Thanks,
Todd Allen
EDPS
Electronic Data Processing Services
tallen@xxxxxxxxxxxx
--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/web400.
midrange.com
