Re: What is more "usual": creating webservice from existing java
class or starting from WSDL definition ?
Jason Stacy wrote:
As well known one can start to create WebServices by two ways:
1.) create a WSDL from an existing java class (with webservice annotations)
or
2.) Create a java class source skeleton from an existing WSDL definition file.
Which approach is more usual?
Does usual == correct?
If webservice projects are started in real world which is preferable ?
If cabinetry projects are started in the real world, which is preferable, to
have a set of plans by which to build the cabinets, or to develop plans based
on actual cabinets one has built before?
There is a time in the development of a WSDL, like any other programming
artifact, where its expression is informed by prototypes and iterative
re-evaluation of successive versions.
Once the WSDL is published it represents a contract that a web service must
follow. So must its clients. Services and their clients will be generated in
accordance with that WSDL thenceforth.
Future generations of the WSDL will be different WSDLs. Backward
compatibility is less achievable, if ever, in the WSDL-web-service world.
Summary: WSDLs might come from annotated classes initially. Classes come
from WSDLs operationally.
Is there a web page which discusses the pros and cons of the two ways ?
GIYF. But there really aren't "pros and cons" as if the different approaches
were somehow contradictory. They're complementary, intended for different
phases of the service's life and different purposes within it.
--
Lew