Overview | Package | Class | Use | Tree | Deprecated | Index | Help
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES

## Package com.bea.wlevs.eventstore

This package is the service provider interface (SPI) for the event repository.

See:
Description

Interface Summary
EventStore | A channel for accessing a collection of persistent events that are to be treated as a unit for purposes of event capture and query.
EventStoreCursor | An iterator over events returned from a query.
EventStoreManager | The top-level event store service, through which clients may interact with event stores.
EventStoreProvider | An underlying repository that provides event store services to clients.
EventStoreQuery | A provider-specific specification of which events a client wishes to retrieve from an event store.
EventStoreTransaction | A context within which event store capture and query operations may be performed atomically and isolated from other transactions.

Class Summary
EventStoreManagerPolicy | Specifies the event store manager policy.
EventStoreProperties | Specifies the desired properties that a newly created event store must have, in order to meet the client's needs.
EventStoreProviderPolicy | Specifies the event store provider policy.

Exception Summary
DuplicateProviderNameException | Exception raised if an attempt is made to register a provider having the same name as a previously registered provider.
EventStoreException | A generic exception raised by the Event Store API.
NoSuitableProviderException | Exception raised if an invalid policy argument is specified.
PolicyValidationException | Exception raised if an invalid policy argument is specified.

## Package com.bea.wlevs.eventstore Description

This package is the service provider interface (SPI) for the event repository.

The Event Repository is organized around Event Stores. Each Event Store is a set of events that are treated as a single collection. Unlike a Java `Collection`, however, the contents of an Event Store is persistent, and may be larger than available memory. In a typical use case, the set of events captured by recording the events flowing along one stream of an Event Processing Network (EPN) would constitute a single Event Store. If two different streams were captured, say at different points within the EPN, or in independent runs of an EPN, each would be a different Event Store.

One or more Event Stores are hosted by an Event Store Provider. One or more Event Store Providers are registered with an Event Store Manager, of which there is at most one in a JVM instance. The Event Store Manager is registered as an OSGi Service, and is the entry point for application access to Event Stores.

An application interacts with an Event Store via an object of type `EventStore`. A application obtains an `EventStore` instance by calling methods of the Event Store Manager, which is a singleton service that implements `EventStoreManager`. An application obtains a reference to the Event Store Manager from the OSGi Service Registry.

The Event Store Manager provides methods to find an existing Event Store, create a new Event Store, or find-or-create (i.e., find an existing Event Store or create a new one if it does not exist); each of these methods returns an `EventStore` instance. The `EventStore` instance provides methods to add events (capture) and retrieve events (query). The interface supports transactions, though not all Event Store Providers may support this.

Overview | Package | Class | Use | Tree | Deprecated | Index | Help
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES

Copyright © 2007 BEA Systems All Rights Reserved.