From d3be414bec59f89f8c2bebeeef000ce905071913 Mon Sep 17 00:00:00 2001 From: Arjen Poutsma Date: Mon, 19 Feb 2007 15:53:14 +0000 Subject: [PATCH] --- src/site/apt/faq.apt | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/src/site/apt/faq.apt b/src/site/apt/faq.apt index de734ffe..6db354d7 100644 --- a/src/site/apt/faq.apt +++ b/src/site/apt/faq.apt @@ -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 <<>>, it will be + exposed as <<>>. (i.e. <<>>).