Package | Description |
---|---|
org.mule.api.endpoint |
Endpoint interfaces.
|
org.mule.config.spring.factories | |
org.mule.endpoint |
Implemtation of Mule endpoint uris.
|
org.mule.module.client |
Simple interface for Mule clients to send and receive events from local or remote Mule Servers.
|
org.mule.transport.soap |
Class and Description |
---|
URIBuilder
This has the following logic:
- if an address is specified, it is used verbatim (except for parameters); this is consistent with the generic case
- otherwise, we construct from components, omitting things that aren't specified as much as possible
(use required attributes to guarantee entries)
In addition, parameters are handled as follows:
- parameters can be given in the uri, the queryMap, or both
- queryMap values override uri values
- the order of parameters in the uri remains the same (even if values change)
- queryMap parameters are appended after uri parameters
(I don't think ordering should matter, but XFire seems to require it)
TODO - check that we have sufficient control via XML (what about empty strings?)
Not called EndpointURIBuilder because of
EndpointURIBuilder |
Class and Description |
---|
AbstractEndpointBuilder
Abstract endpoint builder used for externalizing the complex creation logic of
endpoints out of the endpoint instance itself.
|
EndpointURIEndpointBuilder |
Class and Description |
---|
AbstractEndpoint
ImmutableMuleEndpoint describes a Provider in the Mule Server. |
AbstractEndpointBuilder
Abstract endpoint builder used for externalizing the complex creation logic of
endpoints out of the endpoint instance itself.
|
AbstractEndpointURIBuilder
UrlEndpointURIBuilder is the default endpointUri strategy suitable for
most connectors |
EndpointURIEndpointBuilder |
URIBuilder
This has the following logic:
- if an address is specified, it is used verbatim (except for parameters); this is consistent with the generic case
- otherwise, we construct from components, omitting things that aren't specified as much as possible
(use required attributes to guarantee entries)
In addition, parameters are handled as follows:
- parameters can be given in the uri, the queryMap, or both
- queryMap values override uri values
- the order of parameters in the uri remains the same (even if values change)
- queryMap parameters are appended after uri parameters
(I don't think ordering should matter, but XFire seems to require it)
TODO - check that we have sufficient control via XML (what about empty strings?)
Not called EndpointURIBuilder because of
EndpointURIBuilder |
Class and Description |
---|
MuleEndpointURI
MuleEndpointURI is used to determine how a message is sent of
received. |
Class and Description |
---|
AbstractEndpointURIBuilder
UrlEndpointURIBuilder is the default endpointUri strategy suitable for
most connectors |
Copyright © 2003–2013 MuleSource, Inc.. All rights reserved.