[jboss-cvs] JBossCache/src/org/jboss/cache/config ...

[Manik Surtani]

  User: msurtani
  Date: 07/05/24 09:11:10

  Modified:    src/org/jboss/cache/config  Option.java
  Log:
  Removed ugly and buggy bypassInterceptorChain Option
  
  Revision  Changes    Path
  1.14      +0 -20     JBossCache/src/org/jboss/cache/config/Option.java
  
  (In the diff below, changes in quantity of whitespace are not shown.)
  
  Index: Option.java
  ===================================================================
  RCS file: /cvsroot/jboss/JBossCache/src/org/jboss/cache/config/Option.java,v
  retrieving revision 1.13
  retrieving revision 1.14
  diff -u -b -r1.13 -r1.14
  --- Option.java	10 Jan 2007 17:47:22 -0000	1.13
  +++ Option.java	24 May 2007 13:11:10 -0000	1.14
  @@ -25,26 +25,6 @@
      private boolean forceWriteLock;
   
      /**
  -    * @since 2.0.0
  -    * @deprecated This is very kludgy and ugly.  If you need to work on a {@link org.jboss.cache.Node} directly, use the XXXDirect() methods on {@link org.jboss.cache.NodeSPI}.  This method will disappear before BETA1
  -    */
  -   public boolean isBypassInterceptorChain()
  -   {
  -      return bypassInterceptorChain;
  -   }
  -
  -   /**
  -    * Bypasses the entire interceptor chain and talks to the cache directly.  Use with extreme care, may cause a lot of data corruption and in certain cache configurations, my cause
  -    * the cache not to function at all.  Intended strictly for internal use only.
  -    *
  -    * @deprecated This is very kludgy and ugly.  If you need to work on a {@link org.jboss.cache.Node} directly, use the XXXDirect() methods on {@link org.jboss.cache.NodeSPI}.  This method will disappear before BETA1
  -    */
  -   public void setBypassInterceptorChain(boolean bypassInterceptorChain)
  -   {
  -      this.bypassInterceptorChain = bypassInterceptorChain;
  -   }
  -
  -   /**
       * @since 1.4.0
       */
      public boolean isSuppressLocking()