Examples of Pool

• ch.cmbntr.modulizer.bootstrap.util.Resources.Pool
• com.abiquo.ssm.model.Pool
  A storage pool. @author Ignasi Barrera
• com.axemblr.provisionr.api.pool.Pool
• com.gemstone.gemfire.cache.client.Pool
• com.google.refine.util.Pool
• com.sun.jndi.ldap.pool.Pool
  A map of pool ids to Connections. Key is an object that uniquely identifies a PooledConnection request (typically information needed to create the connection). The definitions of the key's equals() and hashCode() methods are vital to its unique identification in a Pool. Value is a ConnectionsRef, which is a reference to Connections, a list of equivalent connections. Supports methods that - retrieves (or creates as necessary) a connection from the pool - removes expired connections from the pool Connections cleanup: A WeakHashMap is used for mapping the pool ids and Connections. A SoftReference from the value to the key is kept to hold the map entry as long as possible. This allows the GC to remove Connections from the Pool under situations of VM running out of resources. To take an appropriate action of 'closing the connections' before the GC reclaims the ConnectionsRef objects, the ConnectionsRef objects are made weakly reachable through a list of weak references registered with a reference queue. Upon an entry gets removed from the WeakHashMap, the ConnectionsRef (value in the map) object is weakly reachable. When another sweep of clearing the weak references is made by the GC it puts the corresponding ConnectionsWeakRef object into the reference queue. The reference queue is monitored lazily for reclaimable Connections whenever a pooled connection is requested or a call to remove the expired connections is made. The monitoring is done regularly when idle connection timeout is set as the PoolCleaner removes expired connections periodically. As determined by the experiements, cleanup of resources using the ReferenceQueue mechanism is reliable and has immidiate effect than the finalizer approach. @author Rosanna Lee
• com.sun.tools.javac.jvm.Pool
  An internal structure that corresponds to the constant pool of a classfile.

  This is NOT part of any supported API. If you write code that depends on this, you do so at your own risk. This code and its internal interfaces are subject to change or deletion without notice.

• com.thoughtworks.proxy.toys.pool.Pool
  A simple pool implementation that collects its unused components of a specific type automatically.

  The pool will only manage instances that were explicitly passed into the pool before. For more sophisticated pooling strategies, derive from this class or wrap it.

  The implementation will provide these instances wrapped by a proxy, that will return the instance automatically to the pool, if it falls out of scope and is collected by the garbage collector. Since the pool only returns instances wrapped by a proxy that implements the {@link Poolable} interface, this can be used to release th instance manuallyto the pool also. With an implementation of the {@link Resetter} interface each element's status can be reset or theelement can be dropped from the pool at all, if it is exhausted.

  A client can use the pool's monitor for an improved synchronization. Everytime an object is returned to the pool, all waiting Threads of the monitor will be notified. This notification will happen independently of the result of the {@link Resetter#reset(Object)} method.

  @author Jörg Schaible @since 0.2 @see com.thoughtworks.proxy.toys.pool
• com.xensource.xenapi.Pool
  Pool-wide information @author Citrix Systems, Inc.
• etch.bindings.java.support.Pool
  Interface to a queued or free thread pool.
• fr.dyade.aaa.common.Pool
• jnipap.Pool
• org.activiti.bpmn.model.Pool
  @author Tijs Rademakers
• org.apache.avalon.excalibur.pool.Pool
  This is an Pool that caches Poolable objects for reuse. @author Avalon Development Team @version CVS $Revision: 1.6 $ $Date: 2004/03/29 16:50:37 $ @since 4.0
• org.apache.etch.bindings.java.support.Pool
  Interface to a queued or free thread pool.
• org.apache.hadoop.mapred.Pool
  A schedulable pool of jobs.
• org.apache.openejb.util.Pool
  Any successful pop() call requires a corresponding push() or discard() call.

  A pop() call that returns null is considered successful. A null indicates that the calling code has a permit to create a poolable object and call {@link Pool#push(Object)}. This is the only situation in which that method may be called.

  To simply fill the pool without a corresponding pop(), the add() method must be used. This method will attempt to aquire a permit to add to the pool. @version $Rev$ $Date$

• org.apache.provisionr.api.pool.Pool
• org.apache.tapestry.util.pool.Pool
  A Pool is used to pool instances of a useful class. It uses keys, much like a {@link Map}, to identify a list of pooled objects. Retrieving an object from the Pool atomically removes it from the pool. It can then be stored again later. In this way, a single Pool instance can manage many different types of pooled objects, filed under different keys.

  Unlike traditional Pools, this class does not create new instances of the objects it stores (with the exception of simple Java Beans, via {@link #retrieve(Class)}. The usage pattern is to retrieve an instance from the Pool, and if the instance is null, create a new instance.

  The implementation of Pool is threadsafe.

  Pool implements {@link ICleanable}, with a goal of only keeping pooled objects that have been needed within a recent time frame. A generational system is used, where each pooled object is assigned a generation count. {@link #executeCleanup}discards objects whose generation count is too old (outside of a {@link #getWindow() window}).

  Objects in the pool can receive two notifications: one notification when they are {@link #store(Object,Object) stored} into the pool,and one when they are discarded from the pool.

  Classes that implement {@link org.apache.tapestry.util.pool.IPoolable}receive notifications directly, as per the two methods of that interface.

  Alternately, an adaptor for the other classes can be registerered (using {@link #registerAdaptor(Class,IPoolableAdaptor)}. The adaptor will be invoked to handle the notification when a pooled object is stored or discarded. @author Howard Lewis Ship @version $Id: Pool.java 243791 2004-02-19 17:38:13Z hlship $

• org.candlepin.model.Pool
  Represents a pool of products eligible to be consumed (entitled). For every Product there will be a corresponding Pool.
• org.jboss.ejb3.annotation.Pool
  Injection utilities @author Scott.Stark@jboss.org @version $Revision: 93959 $
• org.jboss.ejb3.pool.Pool
  A pool of stateless objects. A pool is linked to an object factory. How this link is established is left beyond scope. @author Carlo de Wolf @version $Revision: $
• org.jboss.jca.common.api.metadata.common.Pool
  A Pool. @author Stefano Maestri
• org.jboss.jca.core.connectionmanager.pool.api.Pool
  A pool. @author Gurkan Erdogdu @author David Jencks @author Jesper Pedersen
• uk.ac.bbsrc.tgac.miso.core.data.Pool
  A Pool represents a collection of one or more {@link Poolable} objects, which enables multiplexing to be modelledif necessary. Pools provide the link between the {@link Sample} tree and the {@link Run} tree of the MISO data model,which means that multiple samples from multiple {@link Project}s can be pooled together.

  Pools are typed by the {@link Poolable} interface type they can accept, and as such, Pools can accept {@link Dilution}and {@link Plate} objects at present. At creation time, a Pool is said to be "ready to run", which makes it easy tocategorise and list Pools according to whether they have been placed on a {@link SequencerPoolPartition} (at whichpoint ready to run becomes false) or not. @author Rob Davey @since 0.0.2

• weblogic.utils.reuse.Pool

Examples of weblogic.utils.reuse.Pool