![]() | com.espertech.esper.common.client Namespace |
[Missing <summary> documentation for "N:com.espertech.esper.common.client"]
Class | Description | |
---|---|---|
![]() | EPCompiled |
The assembly of a compile EPL module or EPL fire-and-forget query.
|
![]() | EPCompiledManifest |
Manifest is part of the and provides information for the runtime that
allows it to use the byte code.
|
![]() | EPException |
This exception is thrown to indicate a problem in administration and runtime.
|
![]() | EPGeneratedAttribute | |
![]() | EPLockException | |
![]() | EPNotSerializableException | |
![]() | EPRuntimeException | |
![]() | EventBeanExtensions | |
![]() | EventPropertyDescriptor |
Descriptor for event property names, property types and access metadata.
|
![]() | EventTypeException |
Indicates that a problem occurred looking up, assigning or creating and event type.
|
![]() | FragmentEventType |
Provides an event type for a property of an event.
A fragment is a property value that is itself an event, or that can be represented
as an event. Thereby a fragment comes with event type metadata and means of querying
the fragment's properties.
A array or collection of property values that is an array of events or that can be
represented as an array of events has the indexed flag set.
A map of property values that is an map of events or that can be represented as a map
of events has the mapped flag set.
|
![]() | PropertyAccessException |
This exception is thrown to indicate a problem with a accessing a property of an EventBean />.
|
![]() | ProxyEventPropertyGetter | |
![]() | ProxyEventPropertyGetterIndexed | |
![]() | ProxyEventPropertyGetterMapped | |
![]() | ProxyEventPropertyValueGetter | |
![]() | ProxyEventPropertyValueGetterGetFunc | |
![]() | SerializableExtensions |
Interface | Description | |
---|---|---|
![]() | EPCompilerPathable |
Marker interface for an object containing information that can be added to the compiler path
|
![]() | EventBean |
Interface for event representation. All events have an .
Events also usually have one or more event properties. This interface allows the querying
of event type, event property values and the underlying event object.
|
![]() | EventBeanFactory |
Factory for EventBean instances given an underlying event object.
Not transferable between engine instances.
|
![]() | EventPropertyGetter |
Get property values from an event instance for a given event property. Instances that
implement this interface are usually bound to a particular
and cannot be used to access instances of a different type.
|
![]() | EventPropertyGetterIndexed | |
![]() | EventPropertyGetterMapped | |
![]() | EventPropertyValueGetter |
Get property values from an event instance for a given event property.
Instances that implement this interface are usually bound to a particular and cannot
be used to access instances of a different type.
|
![]() | EventSender |
Returns a facility to process event objects that are of a known type.
Obtained via the method EPRuntime#getEventSender(String) the sender is specific to a given
event type and may not process event objects of any other event type; See the method documentation for more
details.
|
![]() | EventType |
This interface provides metadata on events.
The interface exposes events as organizations of named values. The contract is that any event in the system must have a name-based way of accessing sub-data within its event type. A simple example is a vanilla: the names can be property names, and those properties can have still more properties beneath them. Another example is a Map structure. Here string names can refer to data objects. The interface presents an immutable view of events. There are no methods to change property values. Events by definition are an observation of a past occurrence or state change and may not be modified. Information on the super-types (superclass and interfaces implemented by native events) is also available, for vanilla events as well as for Map event types that has supertypes. Implementations provide metadata on the properties that an implementation itself provides. Implementations also allow property expressions that may use nested, indexed, mapped or a combination of these as a syntax to access property types and values. Implementations in addition may provide a means to access property values as event fragments, which are typed events themselves. The order of property names depends on the underlying event type and may be platform-specific. When the underlying class is object-array the order of property names is always as-provided. When the underlying class is map the order of property names is defined only when LinkedHashMap was used to register the type. When the underlying class is bean the order of property names is depends on the order of the methods returned by reflection. |