Esper API Documentation

Esper API

See:
          Description

Core API
net.esper.client This package defines the central Esper Client APIs.
net.esper.client.time This package defines the Esper Client timer control events.
net.esper.event This package defines the Esper Client event API.

 

Other Packages
net.esper.collection  
net.esper.core  
net.esper.dispatch  
net.esper.emit  
net.esper.eql.expression  
net.esper.eql.generated  
net.esper.eql.join  
net.esper.eql.join.assemble  
net.esper.eql.join.exec  
net.esper.eql.join.plan  
net.esper.eql.join.rep  
net.esper.eql.join.table  
net.esper.eql.parse  
net.esper.eql.view  
net.esper.event.property  
net.esper.filter  
net.esper.indicator.jmx  
net.esper.indicator.pretty  
net.esper.pattern  
net.esper.pattern.guard  
net.esper.pattern.observer  
net.esper.schedule  
net.esper.timer  
net.esper.type  
net.esper.util  
net.esper.view  
net.esper.view.ext  
net.esper.view.internal  
net.esper.view.stat  
net.esper.view.stat.olap  
net.esper.view.std  
net.esper.view.stream  
net.esper.view.window  

 

Esper API

This documentation concentrates upon the following Core API interfaces:
  • net.esper.client
  • net.esper.client.time
  • net.esper.event


  • These interfaces are fully intended to be exposed to application code.

    The Extension API is intended to be used by application programmers to extend Esper functionality. None of these interfaces are intended to be called by the application - they are called internally by Esper. This API is less stable than the Core API. The safest way to extend functionality is to contribute extensions back to the project; that way extensions will be updated when the Extension API changes.

    Full Esper documentation may be found at esper.sourceforge.org.

    See Also:
    net.esper.client, net.esper.client.time, net.esper.event