-
CH.ifa.draw.framework.Connector
-
archmapper.main.model.architecture.Connector
-
basicrunner.basichelper.Connector
This is a special service that is used in testing Acceptor component in BASIC. This componennt creates a separate thread that tries to connect to BASIC's acceptor. After successfull connection it writes a connectionString to XConnection.
-
com.facebook.presto.spi.Connector
-
com.google.enterprise.connector.spi.Connector
pringframework.org/">Spring to instantiate objects that implement this interface. The implementor MUST provide a Spring XML configuration file named {@code connectorInstance.xml} to control thisprocess. See the package documentation for more details.
A {@code Connector} object is used as something against which toauthenticate, via the {@link #login()} method. By authenticating,one gets a {@link Session}, which then gives access to all other services. Note, this is presumably "superuser", one-time only authentication, not authentication for a given user query session (which takes place via the {@link AuthenticationManager}).
@since 1.0
-
com.google.gwt.thirdparty.org.apache.catalina.Connector
-
com.googlecode.psiprobe.model.Connector
POJO representing a Connector and its RequestProcessors
@author Mark Lewis
-
com.jcraft.jsch.agentproxy.Connector
-
com.opengamma.util.Connector
Connector used to access a resource, such as a database.
See the implementation classes for more information.
This interface is essentially a marker that allows connectors to be identified.
-
com.sun.jdi.connect.Connector
A method of connection between a debugger and a target VM. A connector encapsulates exactly one {@link Transport}. used to establish the connection. Each connector has a set of arguments which controls its operation. The arguments are stored as a map, keyed by a string. Each implementation defines the string argument keys it accepts.
@see LaunchingConnector
@see AttachingConnector
@see ListeningConnector
@see Connector.Argument
@author Gordon Hirsch
@since 1.3
-
com.vaadin.shared.Connector
Interface implemented by all classes that are capable of communicating with the server or the client side.
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.0
-
de.bamberg.ha.api.remote.Connector
The connector interface defines callback functions for all kind of connectors
@author erik.bamberg
-
diva.canvas.connector.Connector
A Connector is a figure that draws itself between two sites on other figures. To do so, it requires two references to sites on other figures.
@version $Id: Connector.java,v 1.9 2005/07/08 19:54:49 cxh Exp $
@author Michael Shilman
@author John Reekie
-
fr.eolya.simplepipeline.connector.Connector
-
info.bliki.api.Connector
wikimedia.org/w/api.php">Wikimedia API
-
javax.resource.spi.Connector
-
net.grinder.communication.Connector
-
org.apache.accumulo.core.client.Connector
Connector connects to an Accumulo instance and allows the user to request readers and writers for the instance as well as various objects that permit administrative operations. The Connector enforces security on the client side by forcing all API calls to be accompanied by user credentials.
-
org.apache.activemq.broker.Connector
A connector creates and manages client connections that talk to the Broker.
-
org.apache.catalina.Connector
A
Connector is a component responsible receiving requests from, and returning responses to, a client application. A Connector performs the following general logic:
- Receive a request from the client application.
- Create (or allocate from a pool) appropriate Request and Response instances, and populate their properties based on the contents of the received request, as described below.
- For all Requests, the
connector
, protocol
, remoteAddr
, response
, scheme
, secure
, serverName
, serverPort
and stream
properties MUST be set. The contentLength
and contentType
properties are also generally set. - For HttpRequests, the
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. - For all Responses, the
connector
, request
, and stream
properties MUST be set. - No additional headers must be set by the Connector for HttpResponses.
- Identify an appropriate Container to use for processing this request. For a stand alone Catalina installation, this will probably be a (singleton) Engine implementation. For a Connector attaching Catalina to a web server such as Apache, this step could take advantage of parsing already performed within the web server to identify the Context, and perhaps even the Wrapper, to utilize in satisfying this Request.
- Call the
invoke()
method of the selected Container, passing the initialized Request and Response instances as arguments. - Return any response created by the Container to the client, or return an appropriate error message if an exception of any type was thrown.
- If utilizing a pool of Request and Response objects, recycle the pair of instances that was just used.
It is expected that the implementation details of various Connectors will vary widely, so the logic above should considered typical rather than normative.
@author Craig R. McClanahan
@version $Revision: 466595 $ $Date: 2006-10-21 23:24:41 +0100 (Sat, 21 Oct 2006) $
-
org.apache.catalina.connector.Connector
Implementation of a Coyote connector for Tomcat 5.x.
@author Craig R. McClanahan
@author Remy Maucherat
@version $Id: Connector.java 1200601 2011-11-10 22:24:17Z kkolinko $
-
org.apache.geronimo.jee.connector.Connector
3.org/2001/XMLSchema}anyType"> <sequence> <element ref="{http://geronimo.apache.org/xml/ns/deployment-1.2}environment" minOccurs="0"/> <element name="resourceadapter" type="{http://geronimo.apache.org/xml/ns/j2ee/connector-1.2}resourceadapterType" maxOccurs="unbounded"/> <element name="adminobject" type="{http://geronimo.apache.org/xml/ns/j2ee/connector-1.2}adminobjectType" maxOccurs="unbounded" minOccurs="0"/> <element ref="{http://geronimo.apache.org/xml/ns/deployment-1.2}service" maxOccurs="unbounded" minOccurs="0"/> </sequence> </restriction> </complexContent> </complexType>
@version $Rev: 815188 $ $Date: 2009-09-15 15:19:02 +0800 (Tue, 15 Sep 2009) $
-
org.apache.jmeter.monitor.model.Connector
-
org.apache.openejb.jee.Connector
The connectorType defines a resource adapter.
-
org.apache.qpid.config.Connector
-
org.apache.qpid.proton.driver.Connector
Client API
@param < C> application supplied context
-
org.apache.sling.mailarchiveserver.api.Connector
-
org.apache.syncope.core.propagation.Connector
Entry point for making requests on underlying connector bundles.
-
org.apache.tuscany.spi.builder.Connector
Implementations are responsible for bridging invocation chains as an assembly is converted to runtime artifacts
@version $$Rev: 451133 $$ $$Date: 2006-09-28 22:31:27 -0700 (Thu, 28 Sep 2006) $$
-
org.camunda.connect.spi.Connector
-
org.drools.grid.io.Connector
-
org.eclipse.ecf.server.generic.app.Connector
-
org.eclipse.gmf.runtime.notation.Connector
-
org.eclipse.jetty.server.Connector
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.
-
org.eclipse.persistence.sessions.Connector
Purpose: Define an interface for supplying TopLink with a
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
-
org.eclipse.uml2.uml.Connector
-
org.exolab.jms.config.Connector
-
org.fluxtream.core.connectors.Connector
-
org.glassfish.jersey.client.spi.Connector
Client transport connector extension contract.
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)
-
org.hornetq.spi.core.remoting.Connector
A Connector is used by the client for creating and controlling a connection.
@author
Tim Fox
-
org.jboss.as.console.client.shared.subsys.messaging.model.Connector
@author Heiko Braun
@date 4/4/12
-
org.jboss.jca.common.api.metadata.ra.Connector
-
org.jboss.jca.common.api.metadata.spec.Connector
-
org.jboss.jca.common.metadata.ra.common.Connector
-
org.jboss.remoting.transport.Connector
ss.bind.address}:8084/?enableTcpNoDelay=false&clientMaxPoolSize=30]]>-->
1 303 304 60000 ${jboss.bind.address} 6666 false 200 org.jboss.remoting.transport.mock.MockServerInvocationHandler 2410
@author
Jeff Haynie
@author
Adrian Brock
@author
David Jencks
@author
Juha Lindfors
@author
Tom Elrod
@version $Revision: 3620 $
@jmx.mbean description = "An MBean wrapper around a ServerInvoker."
@jboss.xmbean
-
org.jpos.iso.Connector
Connector implements ISORequestListener and forward all incoming messages to a given destination MUX, or Channel handling back responses
@author
Alejandro P. Revilla
@version $Revision$ $Date$
@see org.jpos.iso.ISORequestListener
-
org.libreplan.business.common.entities.Connector
Connector entity, represents a connector in order that LibrePlan interchange some data with other application. A connector is identified by a 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
@author Manuel Rego Casasnovas
-
org.modeshape.jcr.spi.federation.Connector
SPI of a generic external connector, representing the interface to an external system integrated with ModeShape. Since it is expected that the documents are well formed (structure-wise), the {@link FederatedDocumentWriter} class should be used. This isthe base class for {@link WritableConnector} and {@link ReadOnlyConnector} which is what connector implementations are expectedto implement.
@author Horia Chiorean (hchiorea@redhat.com)
-
org.modeshape.web.server.Connector
@author kulikov
-
org.mokai.Connector
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 Escobar
-
org.mortbay.jetty.Connector
HTTP Connector. Implementations of this interface provide connectors for the HTTP protocol. A connector receives requests (normally from a socket) and calls the handle method of the Handler object. These operations are performed using threads from the ThreadPool set on the connector. When a connector is registered with an instance of Server, then the server will set itself as both the ThreadPool and the Handler. Note that a connector can be used without a Server if a thread pool and handler are directly provided.
@author gregw
-
org.mule.api.transport.Connector
Connector
is the mechanism used to connect to external systems and protocols in order to send and receive data.
-
org.openengsb.core.api.Connector
Base interface for connector implementations, it makes the transparent setting of domainId and connectorId in background possible. Important for enhancing of EDB events so that the EDB knows from where the change came. See AbstractOpenEngSBConnectorService
-
org.snova.http.client.Connector
@author yinqiwen
-
org.voltdb.catalog.Connector
Export connector (ELT)
-
org.voltdb.compiler.projectfile.ExportsType.Connector
-
pl.balon.gwt.diagrams.client.connector.Connector
Interface representing connector (object which can be connected two another through connection).
@author Michał Baliński (michal.balinski@gmail.com)
-
pl.tecna.gwt.connectors.client.elements.Connector
-
research.connector.Connector
-
vg.modules.notepad.components.connectorComponent.Connector
This class realizes connector between graph model and current file. All methods of this class by need called from EDT only!!!
@author tzolotuhin