Configuring Acceptors |
![]() |
The acceptors of a CDO Server are configured in the cdo-server.xml file. Here's an example:
The following sections describe the various elements and properties.
Table of Contents
| 1 | Element acceptor | ||
| 2 | Element negotiator | ||
Defines an IAcceptor instance.
Please refer to the Net4j Signalling Platform documentation for details about acceptors and connectors.
The type attribute corresponds to the type of an acceptor factory that is contributed via the
org.eclipse.net4j.util.factories extension point with a product group of
org.eclipse.net4j.acceptors.
The remaining attributes depend on the specified type attribute value.
The following values are possible with the shipped distribution (subject to user-supplied extension):
ITCPAcceptor for fast, new I/O based socket connections. The following additional attributes are recognized:
"0.0.0.0" is the default (whole attribute can be omitted) and
tells the socket to listen on all available addresses.
2036 is the default (whole attribute can be omitted).
IWSAcceptor for WebSocket-based connections over HTTP.
IJVMAcceptor for JVM internal (non-socket based ) connections.
Defines an INegotiator instance to be used by the enclosing acceptor element.
Please refer to the Net4j Signalling Platform documentation for details about negotiators and the pluggable security concept
that can be used for authentication and authorization on the transport-level.
The type attribute corresponds to the type of a negotiator factory that is contributed via the
org.eclipse.net4j.util.factories extension point with a product group of org.eclipse.net4j.negotiators.
The remaining attributes depend on the specified type attribute value. The following values are possible with the shipped distribution (subject to user-supplied extension):
user-id: password.