Skip to main content

WSDL on client side

1 reply [Last post]
Anonymous

Hi,

After generating the artifacts for a WS client why is needed the
wsdllocation reference. ?

Is the WSDL needed on runtime ? Why ?

After generation the artifacts is not enough to run the client without a
reference (remote or local to a wsdl) ?

I might see a reason for some validation BUt that should not be optional ?

Regards

Cristian.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Glen Mazza

On 07/30/2012 04:02 AM, Cristian Chiovari wrote:
> Hi,
>
> After generating the artifacts for a WS client why is needed the
> wsdllocation reference. ? Is the WSDL needed on runtime ? Why ? After
> generation the artifacts is not enough to run the client without a
> reference (remote or local to a wsdl) ?

If you look at the generated service artifact, it has a hardcoded
reference to the WSDL. It needs at least for reading in the WS-Policy
statements and finding out the endpoint URI to make the SOAP calls,
perhaps for runtime schema validation as you mention below.

>
> I might see a reason for some validation BUt that should not be optional ?

Yeah, that's optional:
http://www.jroller.com/gmazza/entry/soap_xml_schema_validation

>
> Regards
>
> Cristian.