Why does the JAX-WS client access WSDL at runtime?

After generating the JAX-WS client using wsimport

wsimport -keep WebService.wsdl

Why should JAX-WS look for a wsdl place at runtime?
This is mistake?

I found this great post: JAX-WS Client: what is the right way to access the local WSDL?

but it doesn’t say why we need wsdl at runtime

+4
source share
1 answer

This is mistake?

No, this is not a mistake, but reasonable from a conceptual point of view.

Why should JAX-WS look for a wsdl place at runtime?

WSDL, , , (aka portTypes, types, messages).

. , , , . bindings : SOAP 1.1 1.2 ? , (, ..). . , , .

, , , :

, , ?

, . , WSDL, , WSDL , . JAX-WS , , , , .

, JAX-WS WSDL , . RI wsdlLocation @WebServiceClient .

+5

All Articles