diff --git a/src/docbkx/server.xml b/src/docbkx/server.xml
index d6957baa..dbb447cf 100644
--- a/src/docbkx/server.xml
+++ b/src/docbkx/server.xml
@@ -1030,33 +1030,37 @@ public class AnnotationOrderEndpoint {
Besides implementing the EndpointExceptionResolver interface, which is only a
matter of implementing the resolveException(MessageContext, endpoint, Exception)
- method, you may also use one of the default implementations.
+ method, you may also use one of the provided implementations.
The simplest implementation is the SimpleSoapExceptionResolver, which just
creates a SOAP 1.1 Server or SOAP 1.2 Receiver Fault, and uses the exception message as the fault string.
+ The SimpleSoapExceptionResolver is the default, but it can be overriden by
+ explicitly adding another resolver.
-
- The SoapFaultMappingExceptionResolver is a more sophisticated implementation.
- This resolver enables you to take the class name of any exception that might be thrown and map it to a
- SOAP Fault, like so:
-
-
+
+ <classname>SoapFaultMappingExceptionResolver</classname>
+
+ The SoapFaultMappingExceptionResolver is a more sophisticated implementation.
+ This resolver enables you to take the class name of any exception that might be thrown and map it to a
+ SOAP Fault, like so:
+
+
-
-
-
- org.springframework.oxm.ValidationFailureException=CLIENT,Invalid request
-
+
+
+
+ org.springframework.oxm.ValidationFailureException=CLIENT,Invalid request
+
]]>
-
- The key values and default endpoint use the format faultCode,faultString,locale, where
- only the fault code is required. If the fault string is not set, it will default to the exception message.
- If the language is not set, it will default to English. The above configuration will map exceptions of
- type ValidationFailureException to a client-side SOAP Fault with a fault string
- "Invalid request", as can be seen in the following response:
-
-
+
+ The key values and default endpoint use the format faultCode,faultString,locale, where
+ only the fault code is required. If the fault string is not set, it will default to the exception message.
+ If the language is not set, it will default to English. The above configuration will map exceptions of
+ type ValidationFailureException to a client-side SOAP Fault with a fault string
+ "Invalid request", as can be seen in the following response:
+
+
]]>
SOAP-ENV:Client
@@ -1064,15 +1068,22 @@ public class AnnotationOrderEndpoint {
]]>
]]>
-
- If any other exception occurs, it will return the default fault: a server-side fault with the exception
- message as fault string.
- Finally, it is also possible to annotate exception classes with the @SoapFault
- annotation, to indicate the SOAP Fault that should be returned whenever that exception is thrown.
- The elements of the annotation include a fault code enumeration, fault string or reason, and language. Here
- is an example exception:
-
-
+ If any other exception occurs, it will return the default fault: a server-side fault with the exception
+ message as fault string.
+
+
+
+ <classname>SoapFaultAnnotationExceptionResolver</classname>
+
+ Finally, it is also possible to annotate exception classes with the
+ @SoapFault annotation, to indicate the SOAP Fault that should be returned
+ whenever that exception is thrown. In order for these annotations to be picked up, you need to add the
+ SoapFaultAnnotationExceptionResolver to your application context.
+ The elements of the annotation include a fault code enumeration, fault string or reason, and language.
+ Here is an example exception:
+
+
-
- Whenever the MyBusinessException is thrown with the constructor string
- "Oops!" during endpoint invocation, it will result in the following response:
-
-
-
-
- SOAP-ENV:Server
- Oops!
-
-
+
+
+
+ Whenever the MyBusinessException is thrown with the constructor string
+ "Oops!" during endpoint invocation, it will result in the following response:
+
+
+
+
+ SOAP-ENV:Server
+ Oops!
+
+
]]>