This commit is contained in:
@@ -62,3 +62,21 @@ Frequently Asked Questions
|
||||
|
||||
The solution therefore is quite simple: to remove the newer 1.3 version of the API, from the class path, and replace
|
||||
it with the version supported by your application server.
|
||||
|
||||
* WSDL
|
||||
|
||||
** How do I retrieve the WSDL from a Service? The ?WSDL query parameter does not work.
|
||||
|
||||
The ?WSDL is a way to get a WSDL of a class. In SWS, a service is generally not implemented as a single class, but
|
||||
as a collection of endpoints.
|
||||
|
||||
There are two ways to expose a WSDL:
|
||||
|
||||
* Simply add the WSDL to the root of the WAR, and the file is served normally. This has the disadvantage that the
|
||||
"location" attribute in the WSDL is static, i.e. it does not necessarily reflect the host name of the server. That's
|
||||
why in the airline sample airline-servlet.xml, we define an WsdlDefinitionHandlerAdapterthere, which transforms the
|
||||
location.
|
||||
|
||||
* Use the MessageDispatcherServlet, which is done is the echo sample. Every WsdlDefinition listed in the
|
||||
*-servlet.xml will be exposed under the bean name. So if you define a WsdlDefinition named <<<echo>>>, it will be
|
||||
exposed as <<<echo.wsdl>>>. (i.e. <<<http://localhost:8080/echo/echo.wsdl>>>).
|
||||
|
||||
Reference in New Issue
Block a user