Anne,
I'm not sure what you mean by code-centric, versus WSDL centric. The approach of writing the business functionality first (if it's not already there) and then generating the first WSDL from that, before deploying as a web service, may be thought of as code centric, but is not tightly coupled to anything (in fact, just the opposite).
Or are you talking about WSDL generation (after deployment) versus providing a fixed WSDL (or a WSDL generated in a controlled way) for clients to use?
Tony
Code centricity is a fine approach if your goal is to use SOAP as a slower
replacement for RMI -- producing tightly coupled Java-centric distributed
object applications. (But why not just use RMI?)
If your goal is to develop language-independent, flexible, loosely coupled,
document-oriented, SOA environments, then you should take a WSDL-centric
approach.
Anne
- RE: Best Practice Greg Michalopoulos
- Re: Best Practice Jim Murphy
- Re: Best Practice Joe Plautz
- RE: Best Practice Anne Thomas Manes
- RE: Best Practice Anne Thomas Manes
- RE: Best Practice Ed Saltelli
- Re: Best Practice HG
- Re: Best Practice tony . q . weddle
- Re: Best Practice Paul Libbrecht
- Re: Best Practice Joe Plautz
- RE: Best Practice tony . q . weddle
- RE: Best Practice Anand Natrajan
- Re: Best Practice Dennis Sosnoski
- Re: Best Practice tony . q . weddle
- RE: Best Practice Sagar Pidaparthi
- Re: Best Practice Dennis Sosnoski
- RE: Best Practice Ed Saltelli
- Re: Best Practice HG
- Re: Best Practice Paul Libbrecht