All Element Summary |
abstract-protocol |
Type: |
|
Content: |
empty, 1 attribute |
Subst.Gr: |
|
Defined: |
|
Used: |
|
|
connector |
Connects Mule to a TCP socket to send or receive data via the network.
Type: |
|
Content: |
complex, 16 attributes, attr. wildcard, 7 elements |
Subst.Gr: |
|
Defined: |
|
Used: |
never |
|
custom-class-loading-protocol |
A length protocol that uses a specific class loader to load objects from streams
Type: |
|
Content: |
empty, 4 attributes |
Subst.Gr: |
|
Defined: |
|
Used: |
never |
|
custom-protocol |
The custom-protocol element allows you to configure your own protocol implementation.
Type: |
|
Content: |
empty, 3 attributes |
Subst.Gr: |
|
Defined: |
|
Used: |
never |
|
direct-protocol |
TCP does not guarantee that data written to a socket is transmitted in a single packet.
Type: |
|
Content: |
empty, 2 attributes |
Subst.Gr: |
|
Defined: |
|
Used: |
never |
|
endpoint |
The endpoint element configures a global TCP endpoint definition.
Type: |
|
Content: |
complex, 13 attributes, attr. wildcard, 16 elements |
Subst.Gr: |
|
Defined: |
|
Used: |
never |
|
eof-protocol |
TCP does not guarantee that data written to a socket is transmitted in a single packet, so if you want to transmit entire Mule messages reliably, you must specify an additional protocol.
Type: |
|
Content: |
empty, 2 attributes |
Subst.Gr: |
|
Defined: |
|
Used: |
never |
|
inbound-endpoint |
The inbound-endpoint element configures the endpoint on which the messages are received.
Type: |
|
Content: |
complex, 13 attributes, attr. wildcard, 16 elements |
Subst.Gr: |
|
Defined: |
|
Used: |
never |
|
length-protocol |
The length-protocol element configures the length protocol, which precedes each message with the number of bytes sent so that an entire message can be constructed on the received.
Type: |
|
Content: |
empty, 3 attributes |
Subst.Gr: |
|
Defined: |
|
Used: |
never |
|
outbound-endpoint |
The outbound-endpoint element configures the endpoint where the messages are sent.
Type: |
|
Content: |
complex, 13 attributes, attr. wildcard, 16 elements |
Subst.Gr: |
|
Defined: |
|
Used: |
never |
|
polling-connector |
Connects Mule to a TCP socket to send or receive data via the network.
Type: |
|
Content: |
complex, 18 attributes, attr. wildcard, 7 elements |
Subst.Gr: |
|
Defined: |
|
Used: |
never |
|
safe-protocol |
Similar to length-protocol, safe-protocol also includes a prefix.
Type: |
|
Content: |
empty, 3 attributes |
Subst.Gr: |
|
Defined: |
|
Used: |
never |
|
streaming-protocol |
TCP does not guarantee that data written to a socket is transmitted in a single packet, so if you want to transmit entire Mule messages reliably, you must specify an additional protocol.
Type: |
|
Content: |
empty, 1 attribute |
Subst.Gr: |
|
Defined: |
|
Used: |
never |
|
xml-eof-protocol |
Similar to xml-protocol, the xml-eof-protocol element configures the XML protocol, but it will also use socket closure to terminate a message (even if the XML is not well-formed).
Type: |
|
Content: |
empty, 1 attribute |
Subst.Gr: |
|
Defined: |
|
Used: |
never |
|
xml-protocol |
TCP does not guarantee that data written to a socket is transmitted in a single packet, so if you want to transmit entire Mule messages reliably, you must specify an additional protocol.
Type: |
|
Content: |
empty, 1 attribute |
Subst.Gr: |
|
Defined: |
|
Used: |
never |
|