|
Spring Web Services Framework | |||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | |||||||||
public interface EndpointMapping
Defines a mapping between message requests and endpoint objects.
This class can be implemented by application developers, although this is not always necessary, asPayloadRootQNameEndpointMapping and SoapActionEndpointMapping are included.
HandlerMapping implementations can support mapped interceptors but do not have to. An endpoint will always be wrapped
in a EndpointExecutionChain instance, optionally accompanied by some EndpointInterceptor
instances. The MessageDispacher will first call each EndpointInterceptor's
handlerRequest method in the given order, finally invoking the endpoint itself if all
handlerRequest methods have returned true.
AbstractEndpointMapping,
PayloadRootQNameEndpointMapping,
SoapActionEndpointMapping| Method Summary | |
|---|---|
EndpointInvocationChain |
getEndpoint(MessageContext messageContext)
Returns an endpoint and any interceptors for this message context. |
| Method Detail |
|---|
EndpointInvocationChain getEndpoint(MessageContext messageContext)
throws Exception
EndpointExecutionChain contains an endpoint Object, rather than even a tag interface,
so that endpoints are not constrained in any way. For example, a EndpointAdapter could be written to
allow another framework's endpoint objects to be used.
Returns null if no match was found. This is by design. The MessageDispatcher will query
all registered EndpointMapping beans to find a match, and only decide there is an error if none can
find an endpoint.
null if
no mapping is found
Exception - if there is an internal error
|
Spring Web Services Framework | |||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | |||||||||