> people try to expose legacy application of similar nature. Doing
> good RESTful design over complex legacy API is not easy and for vast
> majority of developers it's faster to 'map' legacy operations to
> WSDL with minimal modifications. And if you add available tooling...
> If the WSDL-based code generation is well done then such code
> survives reasonable (backward compatible) interface changes. There
> is nothing wrong with this - except that the generated code is often
> bad... ;-)
I am sure we'll find a niche for WSDL sooner or later. Just hold on a
bit longer. It seems every WS-* advocate for SOA has a different story
about what SOA is, why WSDL is great, etc.
Again, I was walling off legacy systems using earlier technology very
well when WSDL was not even a glimmer in some grad students eyes. So I
see no reason to invest in it for that reason either.
-Patrick
SPONSORED LINKS
| Computer software | Computer aided design software | Computer job |
| Soa | Service-oriented architecture |
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
