Interface | Description |
---|---|
IAdmin |
Administration interface providing access to admin-only functionality as well
as JMX-based server access and selected user functions.
|
IAnalysis |
Provides access to the model objects involved in analysis.
|
IConfig |
Access to server configuration.
|
IContainer |
Provides methods for dealing with the core "Pojos" of OME.
|
IDelete |
Provides simplifed methods for deleting instances from the database.
|
ILdap |
Administration interface providing access to admin-only functionality as well
as JMX-based server access and selected user functions.
|
IMetadata |
Provides method to interact with acquisition metadata and
annotations.
|
IPixels |
Metadata gateway for the
RenderingEngine and
clients. |
IProjection |
Provides methods for performing projections of Pixels sets.
|
IQuery |
Provides methods for directly querying object graphs.
|
IRenderingSettings |
Provides method to apply rendering settings to a collection of images.
|
IRepositoryInfo |
Provides methods for obtaining information for server repository disk space
allocation.
|
IScale |
Provides methods for performing scaling (change of the image size through
interpolation or other means) on BufferedImages.
|
ISession |
Start here:
Session creation service for OMERO. |
IShare | Deprecated |
ITypes |
Access to reflective type information.
|
IUpdate |
Provides methods for directly updating object graphs.
|
JobHandle |
Allows submission of asynchronous jobs.
|
RawFileStore |
Raw file gateway which provides access to the OMERO file repository.
|
RawPixelsStore |
Binary data provider.
|
Search |
Central search interface, allowing Web2.0 style queries.
|
ServiceInterface |
Marker interface representing an OMERO API Interface.
|
StatefulServiceInterface |
OMERO API Interface with stateful semantics.
|
ThumbnailStore |
Provides methods for dealing with thumbnails.
|
The API as outlined by this package will be made available to all programming languages supported by Omero. Other "local" apis are available for server only programming.
The interfaces contained here are also specially marked in order to allow special processing by the container. StatefulServiceInterface, for example, allows for the triggering of container events on creation and destruction of a non-singleton service.