See the implementation classes for more information.
This interface is essentially a marker that allows connectors to be identified.
A connector consists of a shared state (server sets the state and automatically communicates changes to the client) and the possibility to do RPC calls either from the server to the client or from the client to the server.
No classes should implement this interface directly, client side classes wanting to communicate with server side should implement {@link com.vaadin.client.ServerConnector} and server side classes shouldimplement {@link com.vaadin.server.ClientConnector}.
@author Vaadin Ltd @since 7.0.0connector
, protocol
, remoteAddr
, response
, scheme
, secure
, serverName
, serverPort
and stream
properties MUST be set. The contentLength
and contentType
properties are also generally set. method
, queryString
, requestedSessionCookie
, requestedSessionId
, requestedSessionURL
, requestURI
, and secure
properties MUST be set. In addition, the various addXxx
methods must be called to record the presence of cookies, headers, and locales in the original request. connector
, request
, and stream
properties MUST be set. invoke()
method of the selected Container, passing the initialized Request and Response instances as arguments. A {@link Connector} accept connections and data from remote peers,and allows applications to send data to remote peers, by setting up the machinery needed to handle such tasks.
Connection
to a JDBC database. Description: This interface defines the methods to be implemented that allow TopLink to acquire a Connection
to a JDBC database. There are only 2 methods that need to be implemented:
java.sql.Connection connect(java.util.Properties properties)
void toString(java.io.PrintWriter writer)
Once these methods have been implemented, an instance of the new Connector
can be passed to a JDBCLogin
at startup. For example: session.getLogin().setConnector(new FooConnector());
session.login();
@see DatabaseLogin
@author Big Country
@since TOPLink/Java 2.1
Note that unlike most of the other {@link org.glassfish.jersey.spi.Contract Jersey SPI extension contracts}, Jersey {@code Connector} is not a typical runtime extension and as such cannot be directly registeredusing a configuration {@code register(...)} method. Jersey client runtime retrieves a {@code Connector}instance upon Jersey client runtime initialization using a {@link org.glassfish.jersey.client.spi.ConnectorProvider}registered in {@link org.glassfish.jersey.client.ClientConfig}.
@author Marek Potociar (marek.potociar at oracle.com)name
and it has a list of pairs key-value in order to store the configuration parameters of the connector. This entity should be used to create new connectors in LibrePlan.
@author Miciele Ghiorghis Marker interface implemented by connectors.
When a processor is added to the the {@link org.mokai.RoutingEngine}, it is wrapped into a {@link org.mokai.ConnectorService}.
@author German EscobarConnector
is the mechanism used to connect to external systems and protocols in order to send and receive data.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|