Another reason a client can benefit from using a wsdl is that it might bring extra uptodate information for the client policy
engine, extra alternative endpoints, etc...
Cheers, Sergey
----- Original Message -----
From: "Daniel Kulp" <[EMAIL PROTECTED]>
To: <cxf-user@incubator.apache.org>
Sent: Friday, May 04, 2007 2:23 PM
Subject: Re: Why does a JAX-WS client use the WSDL at run time?
On Thursday 03 May 2007 21:55, Steven E. Harris wrote:
Daniel Kulp <[EMAIL PROTECTED]> writes:
> Technically, with JAX-WS, you don't need the wsdl. However, the
> spec does say that if it's available/specified, we're supposed to
> use it.
Use it to supply default values? It seems like a large run time tax
that the WSDL2Java tool -- or something like it -- should be fixing
into code.
There's a couple places it's really used. One is the actual connection
information. The URL isn't burned in anywhere. The other thing that
is done is to make sure the WSDL actually matches the code. For
example, does the interface that you are using actually have matching
operations in the wsdl.
On the server side, if the original WSDL is available, we return it
during ?wsdl processing rather than synthesize one.
.............
> You would still need to set the endpoint address though. That
> doesn't get recorded anywhere.
Oh, as that normally gets read from the WSDL at run time, not from an
annotation on the Service-derived class, right?
Right.
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727 C: 508-380-7194
[EMAIL PROTECTED]
http://www.dankulp.com/blog
