Uses of Package
org.eclipse.emf.cdo.server
Package
Description
Server integration of the CDO Lifecycle Management.
Server concepts for dealing with repositories and stores.
Server side of the protocol to administer CDO repositories remotely.
Server concepts for dealing with DB stores and accessors.
Server concepts for dealing with mapping strategies and mappings for classes, lists and types.
Server concepts for dealing with Net4j-based repositories and fail-over infrastructure.
Server concepts for dealing with DB stores and accessors.
Server concepts for dealing with in-memory stores.
Server concepts for dealing with MongoDB stores and accessors.
Server concepts for dealing with Net4j-based repositories and fail-over infrastructure.
Server implementation of a generic OCL query handler.
Server integration of the
Security
model.Server provider interfaces (SPI) for the protocol to administer CDO repositories remotely.
Server provider interfaces (SPI) for the server integration of the
Security
model.Server service provider interfaces and useful base implementations.
Server provider interfaces (SPI) for CDO
workspaces
.Concepts to checkout, open and further operate CDO
workspaces
.-
-
ClassDescriptionA CDO repository.Represents the state of a single, logical commit operation which is driven through multiple calls to several methods on the
IStoreAccessor
API. -
ClassDescriptionA simple HTTP server that web browsers can connect to in order to render internal server data for debugging purposes.An abstract base implementation of a
server browser page
.Aserver browser
for the repositories in amanaged container
.Represents pluggable content for aserver browser
.Aserver browser page
that rendersrevisions
.Exports the complete contents of arepository
in a format suitable forimports
into new repositories.Imports the complete contents of arepository
from the output created by aexporter
into a new repository.Persists the data that has been read by aimporter
into a newrepository
.Manages all persistent aspects of durable CDO views and provides for vetoableinterception
of the durable view resumption process.A call-back interface primarily intended to allow implementers to prevent the view from being opened by throwing an exception.Represents the execution state of aquery
in the server towards aquery handler
.A query language handler that is capable of executing aquery
.Provides the consumer withquery handlers
that are capable of executingqueries
represented by specificquery infos
.A CDO repository.A marker interface to indicate valid arguments toIRepository.addHandler(Handler)
andIRepository.removeHandler(Handler)
.Provides a way to handle revisions that are to be sent to the client.Protects arepository
by authenticating users and, optionally, authorizing read and write operations.Synchronizes asynchronizable repository
with a master repository.The server-side representation of a clientsession
.Manages the usersessions
of arepository
.Represents the physical data storage back-end of a CDOrepository
, such as a database or a file system folder.Enumerates the possible data formats astore
can accept for commit operations.Enumerates the possible branching options astore
can accept.Enumerates the possible history recording options astore
can accept.Represents a connection to a physical data storage back-end.Represents the state of a single, logical commit operation which is driven through multiple calls to several methods on theIStoreAccessor
API.A data and result context for the modifications inIStoreAccessor.CommitContext.modify(Consumer)
.An extension interface forstore accessors
that support durable locking.Represents the query execution state of aresources query
.Represents the query execution state of aXRefs query
.An extension interface forstore accessors
that support raw data access as needed byrepository synchronizers
orserver importers
.Readschunks
ofpartially loaded
lists from a physical data storage backend.Represents asublist
of consecutive elements that are subject to partial collection loading.A repository with the ability tosynchronize
its content with another repository.The server-side representation of a clienttransaction
.The server-side representation of a clientview
.AnIllegalStateException
that can be thrown fromStoreThreadLocal.getSession()
. -
-
ClassDescriptionProvides the consumer with
query handlers
that are capable of executingqueries
represented by specificquery infos
.The server-side representation of a clientsession
.Represents the physical data storage back-end of a CDOrepository
, such as a database or a file system folder.Represents a connection to a physical data storage back-end.An extension interface forstore accessors
that support raw data access as needed byrepository synchronizers
orserver importers
.An extension interface forstore accessors
that support raw data access as needed byrepository synchronizers
orserver importers
.An extension interface forstore accessors
that support units.Readschunks
ofpartially loaded
lists from a physical data storage backend.The server-side representation of a clienttransaction
. -
ClassDescriptionRepresents the state of a single, logical commit operation which is driven through multiple calls to several methods on the
IStoreAccessor
API.Represents the query execution state of aresources query
.Represents the query execution state of aXRefs query
.Represents asublist
of consecutive elements that are subject to partial collection loading. -
ClassDescriptionA CDO repository.Represents the physical data storage back-end of a CDO
repository
, such as a database or a file system folder. -
ClassDescriptionProvides the consumer with
query handlers
that are capable of executingqueries
represented by specificquery infos
.The server-side representation of a clientsession
.Represents the physical data storage back-end of a CDOrepository
, such as a database or a file system folder.Represents a connection to a physical data storage back-end.An extension interface forstore accessors
that support durable locking.An extension interface forstore accessors
that support durable locking.Readschunks
ofpartially loaded
lists from a physical data storage backend.The server-side representation of a clienttransaction
. -
ClassDescriptionRepresents the physical data storage back-end of a CDO
repository
, such as a database or a file system folder. -
ClassDescriptionProvides the consumer with
query handlers
that are capable of executingqueries
represented by specificquery infos
.Represents the physical data storage back-end of a CDOrepository
, such as a database or a file system folder.Represents a connection to a physical data storage back-end. -
ClassDescriptionProvides the consumer with CDO
repositories
specified by their name.Synchronizes asynchronizable repository
with a master repository.A repository with the ability tosynchronize
its content with another repository. -
ClassDescriptionRepresents the execution state of a
query
in the server towards aquery handler
.A query language handler that is capable of executing aquery
.Represents a connection to a physical data storage back-end. -
-
-
ClassDescriptionRepresents the state of a single, logical commit operation which is driven through multiple calls to several methods on the
IStoreAccessor
API. -
ClassDescriptionManages all persistent aspects of durable CDO views and provides for vetoable
interception
of the durable view resumption process.Provides the protection level ofrevisions
in the context of a specific user.A query language handler that is capable of executing aquery
.Provides the consumer withquery handlers
that are capable of executingqueries
represented by specificquery infos
.A CDO repository.A marker interface to indicate valid arguments toIRepository.addHandler(Handler)
andIRepository.removeHandler(Handler)
.Provides a way to handle commits that are received from a client.Creates CDOrepositories
.Protects arepository
by authenticating users and, optionally, authorizing read and write operations.Provides the consumer with CDOrepositories
specified by their name.Synchronizes asynchronizable repository
with a master repository.The server-side representation of a clientsession
.Manages the usersessions
of arepository
.Represents the physical data storage back-end of a CDOrepository
, such as a database or a file system folder.Enumerates the possible data formats astore
can accept for commit operations.Enumerates the possible branching options astore
can accept.Enumerates the possible history recording options astore
can accept.Represents a connection to a physical data storage back-end.Represents the state of a single, logical commit operation which is driven through multiple calls to several methods on theIStoreAccessor
API.Represents the query execution state of aresources query
.Represents the query execution state of aresources query
that is supposed to deliver one exact resource, ornull
.Readschunks
ofpartially loaded
lists from a physical data storage backend.Represents asublist
of consecutive elements that are subject to partial collection loading.Createsstores
.A repository with the ability tosynchronize
its content with another repository.The server-side representation of a clienttransaction
.The server-side representation of a clientview
. -
ClassDescriptionAn extension interface for
store accessors
that support raw data access as needed byrepository synchronizers
orserver importers
. -
ClassDescriptionRepresents the physical data storage back-end of a CDO
repository
, such as a database or a file system folder.