Examples of EventManager

• com.alibaba.jstorm.event.EventManager
• com.alipay.bluewhale.core.event.EventManager
• com.caucho.config.event.EventManager
  Internal implementation for a Bean
• com.din.din.webapp.beans.interfaces.EventManager
• com.firefly.net.EventManager
• com.ipc.oce.events.EventManager
  Менеджер выгрузки и получения "журнала регистраций" 1С (EventLog). Алгоритм: 1) выгрузка файла EventLog в формате XML на хост 1С 2) "подхватывание" файла в текстовом режиме 3) удаление файла @author Konovalov
• com.khorn.terraincontrol.forge.events.EventManager
  Translates TerrainControl events into MinecraftForge terrain events.
• com.subgraph.orchid.events.EventManager
• com.vmware.vim25.mo.EventManager
  blecloud.org)
• com.zenesis.qx.event.EventManager
  Manages events and listeners on arbitrary objects. The listeners are stored as values in a WeakHashMap where the key is the object to listen to. The value of the map is either: a) an instance of NamedEventListener, b) a small array of NamedEventListeners, or c) a HashMap where the key is the name of the event and the value is the listener. The NamedEventListener's listener object is either a small array of EventListener's or a LinkedHashSet of EventListeners. The reason for using Objects and reflection instead of always using HashMap and LinkedHashSet is to keep the overhead down and support the common use case where an object will have only a few events listened to, and each event will only be listened to by a single piece of code (this is pure hypothesis!). @author John Spackman [john.spackman@zenesis.com]
• de.innovationgate.wgpublisher.events.EventManager
• de.iritgo.aktera.event.EventManager
  The event manager handles the registration of events and their dispatching to event handlers when they are fired.
• de.sciss.app.EventManager
  A custom event dispatcher which carefully deals with synchronization issues. Assuming, the synchronization requests specified for some methods are fulfilled, this class is completely thread safe.

  It is constructed using a second object, the manager's processor which will be invoked whenever new events are available in the event FIFO queue. the processor is then responsible for querying all registered listeners and calling their appropriate event listening methods.

  Event dispatching is deferred to the Swing thread execution time since this makes the whole application much more predictable and easily synchronizable. @author Hanns Holger Rutz @version 0.18, 08-Apr-08

• gnu.classpath.jdwp.event.EventManager
  Manages event requests and filters event notifications. The purpose of this class is actually two-fold: 1) Maintain a list of event requests from the debugger 2) Filter event notifications from the VM If an event request arrives from the debugger, the back-end will call {@link #requestEvent}, which will first check for a valid event. If it is valid, EventManager will record the request internally and register the event with the virtual machine, which may choose to handle the request itself (as is likely the case with breakpoints and other execution-related events), or it may decide to allow the EventManager to handle notifications and all filtering (which is convenient for other events such as class (un)loading). @author Keith Seitz (keiths@redhat.com)
• net.aufdemrand.denizen.events.EventManager
• net.sf.robocode.host.events.EventManager
  This class is used for managing the event queue for a robot. @author Mathew A. Nelson (original) @author Flemming N. Larsen (contributor) @author Matthew Reeder (contributor) @author Robert D. Maupin (contributor) @author Nathaniel Troutman (contributor) @author Pavel Savara (contributor)
• org.apache.cayenne.event.EventManager
  This class acts as bridge between an Object that wants to inform others about its current state or a change thereof (Publisher) and a list of objects interested in the Subject (Listeners). @author Dirk Olmes @author Holger Hoffstaette @author Andrus Adamchik
• org.apache.cocoon.portal.event.EventManager

  Service to manage event notification. The designed has been inspired by the paper by Gupta, S., J. M. Hartkopf, and S. Ramaswamy, in Java Report, Vol. 3, No. 7, July 1998, 19-36, "Event Notifier: A Pattern for Event Notification".

  EventManager brokers events between a Publisher, which produces events, and a Subscriber, which handles the notification of events. A Filter discards events not of interest to a subscriber. All Events have a common ancestor type Event and the event types are identified by a Class.

  @author Carsten Ziegeler @author Volker Schmitt @author Mauro Talevi @version CVS $Id: EventManager.java 30932 2004-07-29 17:35:38Z vgritsenko $
• org.apache.ivy.core.event.EventManager
• org.b3log.latke.event.EventManager
  Event manager. @author Liang Ding @version 1.0.0.3, Jun 23, 2011
• org.eclipse.osgi.framework.eventmgr.EventManager
  te an EventManager with a name for an asynchronous event dispatch thread EventManager eventManager = new EventManager("SomeEvent Async Event Dispatcher Thread"); // Create a CopyOnWriteIdentityMap to hold the list of SomeEventListeners Map eventListeners = new CopyOnWriteIdentityMap(); // Add a SomeEventListener to the listener list eventListeners.put(someEventListener, null); // Asynchronously deliver a SomeEvent to registered SomeEventListeners // Create the listener queue for this event delivery ListenerQueue listenerQueue = new ListenerQueue(eventManager); // Add the listeners to the queue and associate them with the event dispatcher listenerQueue.queueListeners(eventListeners.entrySet(), new EventDispatcher() { public void dispatchEvent(Object eventListener, Object listenerObject, int eventAction, Object eventObject) { try { (SomeEventListener)eventListener.someEventOccured((SomeEvent)eventObject); } catch (Throwable t) { // properly log/handle any Throwable thrown by the listener } } }); // Deliver the event to the listeners. listenerQueue.dispatchEventAsynchronous(0, new SomeEvent()); // Remove the listener from the listener list eventListeners.remove(someEventListener); // Close EventManager to clean when done to terminate async event dispatch thread. // Note that closing the event manager while asynchronously delivering events // may cause some events to not be delivered before the async event dispatch // thread terminates eventManager.close();

  At first glance, this package may seem more complicated than necessary but it has support for some important features. The listener list supports companion objects for each listener object. This is used by the OSGi framework to create wrapper objects for a listener which are passed to the event dispatcher. The ListenerQueue class is used to build a snap shot of the listeners prior to beginning event dispatch. The OSGi framework uses a 2 level listener list for each listener type (4 types). Level one is managed per framework instance and contains the list of BundleContexts which have registered a listener. Level 2 is managed per BundleContext for the listeners in that context. This allows all the listeners of a bundle to be easily and atomically removed from the level one list. To use a "flat" list for all bundles would require the list to know which bundle registered a listener object so that the list could be traversed when stopping a bundle to remove all the bundle's listeners. When an event is fired, a snapshot list (ListenerQueue) must be made of the current listeners before delivery is attempted. The snapshot list is necessary to allow the listener list to be modified while the event is being delivered to the snapshot list. The memory cost of the snapshot list is low since the ListenerQueue object uses the copy-on-write semantics of the CopyOnWriteIdentityMap. This guarantees the snapshot list is never modified once created. The OSGi framework also uses a 2 level dispatch technique (EventDispatcher). Level one dispatch is used by the framework to add the level 2 listener list of each BundleContext to the snapshot in preparation for delivery of the event. Level 2 dispatch is used as the final event deliverer and must cast the listener and event objects to the proper type before calling the listener. Level 2 dispatch will cancel delivery of an event to a bundle that has stopped between the time the snapshot was created and the attempt was made to deliver the event.

  The highly dynamic nature of the OSGi framework had necessitated these features for proper and efficient event delivery. @since 3.1 @noextend This class is not intended to be subclassed by clients.

• org.jboss.forge.furnace.event.EventManager
  Responsible for handling event propagation. @author Lincoln Baxter, III
• org.mitre.sim.event.EventManager
  Operations on the main event queue.
  

  
  Copyright © 2003-2004 The MITRE Corporation

• org.rhq.core.pc.event.EventManager
  Manager for the Plugin Container's Event subsystem. @author Ian Springer
• org.rsbot.event.EventManager
• org.spout.api.event.EventManager
• org.switchyard.internal.EventManager
  Handles registration and publication of events in a ServiceDomain.
• org.w3c.tools.timers.EventManager
  This implements an event manager for timer events. Timer events are a way to have events occur some time in the future. They are an alternative to using separate threads which issue sleep requests themselves.
• wecui.fevents.EventManager
  This class doesn't actually need to exist, but it feels wrong to have this part of the event call logic inside Event @author lahwran

Examples of wecui.fevents.EventManager