Spring/spring-ws
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Corrected Javadoc typo ('endoints' -> 'endpoints').

Browse Source
This commit is contained in:
Rick Evans
2007-05-24 18:10:58 +00:00
parent e1b804e922
commit 8a6d824062
1 changed files with 21 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

33
core/src/main/java/org/springframework/ws/server/MessageDispatcher.java
View File

@@ -41,18 +41,27 @@ import org.springframework.ws.transport.WebServiceMessageReceiver;
import org.springframework.ws.transport.support.DefaultStrategiesHelper;
/**
* Central dispatcher for use within Spring-WS. Dispatches Web service messages to registered endoints.
* <p/>
* This dispatcher is quite similar to Spring MVCs <code>DispatcherServlet</code>. Just like it's counterpart, this
* dispatcher is very flexible. <ul> <li>It can use any <code>EndpointMapping</code> implementation - whether standard,
* or provided as part of an application - to control the routing of request messages to endpoint objects. Endpoint
* mappings can be registered using the <code>endpointMappings</code> property.</li> <li>It can use any
* <code>EndpointAdapter</code>; this allows to use any endpoint interface or form. Default are
* <code>MessageEndpointAdapter</code> and <code>PayloadEndpointAdapter</code>, for <code>MessageEndpoint</code> and
* <code>PayloadEndpoint</code>, respectively. Additional endpoint adapters can be added through the
* <code>endpointAdapters</code> property.</li> <li>Its exception resolution strategy can be specified via a
* <code>EndpointExceptionResolver</code>, for example mapping certain exceptions to SOAP Faults. Default is none.
* Additional exception resolvers can be added through the <code>endpointExceptionResolvers</code> property.</li> </ul>
* Central dispatcher for use within Spring-WS, dispatching Web service messages to
* registered endpoints.
*
* <p>This dispatcher is quite similar to Spring MVCs <code>DispatcherServlet</code>.
* Just like its counterpart, this dispatcher is very flexible.
*
* <ul>
* <li>It can use any <code>EndpointMapping</code> implementation - whether standard,
* or provided as part of an application - to control the routing of request messages
* to endpoint objects. Endpoint mappings can be registered using the
* <code>endpointMappings</code> property.</li>
* <li>It can use any <code>EndpointAdapter</code>; this allows one to use any endpoint
* interface or form. Defaults to the <code>MessageEndpointAdapter</code> and
* <code>PayloadEndpointAdapter</code>, for <code>MessageEndpoint</code> and
* <code>PayloadEndpoint</code>, respectively. Additional endpoint adapters can be
* added through the <code>endpointAdapters</code> property.</li>
* <li>Its exception resolution strategy can be specified via a
* <code>EndpointExceptionResolver</code>, for example mapping certain exceptions to
* SOAP Faults. Default is none. Additional exception resolvers can be added through
* the <code>endpointExceptionResolvers</code> property.</li>
* </ul>
*
* @author Arjen Poutsma
* @see EndpointMapping