[infinispan-commits] Infinispan SVN: r963 - trunk/core/src/main/java/org/infinispan/notifications.

[infinispan-commits at lists.jboss.org]

Author: manik.surtani at jboss.com
Date: 2009-10-16 07:31:38 -0400 (Fri, 16 Oct 2009)
New Revision: 963

Modified:
   trunk/core/src/main/java/org/infinispan/notifications/Listener.java
Log:
Javadoc correction

Modified: trunk/core/src/main/java/org/infinispan/notifications/Listener.java
===================================================================
--- trunk/core/src/main/java/org/infinispan/notifications/Listener.java	2009-10-16 11:26:40 UTC (rev 962)
+++ trunk/core/src/main/java/org/infinispan/notifications/Listener.java	2009-10-16 11:31:38 UTC (rev 963)
@@ -51,7 +51,7 @@
  * addition, any locks acquired for the operation being performed will still be held for the callback.  This needs to be
  * kept in mind as locks may be held longer than necessary or intended to and may cause deadlocking in certain
  * situations.  See above paragraph on long-running tasks that should be run in a separate thread. </p> <b>Note</b>:
- * Since 3.0, a new parameter, <tt>sync</tt>, has been introduced on this annotation.  This defaults to <tt>true</tt>
+ * The <tt>sync</tt> parameter on this annotation defaults to <tt>true</tt>
  * which provides the above semantics.  Alternatively, if you set <tt>sync</tt> to <tt>false</tt>, then invocations are
  * made in a <i>separate</i> thread, which will not cause any blocking on the caller or network thread.  The separate
  * thread is taken from a pool, which can be configured using {@link org.infinispan.config.GlobalConfiguration#setAsyncListenerExecutorProperties(java.util.Properties)}