public interface EndpointMapping
This class can be implemented by application developers, although this is not always necessary, as
SoapActionEndpointMapping are included.
HandlerMapping implementations can support mapped interceptors but do not have to. An endpoint will always be wrapped
EndpointExecutionChain instance, optionally accompanied by some
MessageDispacher will first call each
handlerRequest method in the
given order, finally invoking the endpoint itself if all
handlerRequest methods have returned
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.
null if no match was found. This is by design. The
MessageDispatcher will query all
EndpointMapping beans to find a match, and only decide there is an error if none can find an
nullif no mapping is found
Exception- if there is an internal error
Copyright © 2022 Pivotal Software. All rights reserved.