[jboss-cvs] JBossCache/etc/META-INF ...

[Manik Surtani]

  User: msurtani
  Date: 06/09/11 13:02:42

  Modified:    etc/META-INF  buddyreplication-service.xml
  Log:
  - fixed Data Gravitation interceptor breakages
  - correctly implemented cache.gravidateData()
  - set DummyTM in buddy-replication-service.xml
  
  Revision  Changes    Path
  1.8       +141 -141  JBossCache/etc/META-INF/buddyreplication-service.xml
  
  (In the diff below, changes in quantity of whitespace are not shown.)
  
  Index: buddyreplication-service.xml
  ===================================================================
  RCS file: /cvsroot/jboss/JBossCache/etc/META-INF/buddyreplication-service.xml,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -b -r1.7 -r1.8
  --- buddyreplication-service.xml	6 Sep 2006 19:31:56 -0000	1.7
  +++ buddyreplication-service.xml	11 Sep 2006 17:02:42 -0000	1.8
  @@ -24,7 +24,7 @@
           <!--
               Configure the TransactionManager
           -->
  -        <attribute name="TransactionManagerLookupClass">org.jboss.cache.JBossTransactionManagerLookup</attribute>
  +      <attribute name="TransactionManagerLookupClass">org.jboss.cache.DummyTransactionManagerLookup</attribute>
   
   
           <!--
  @@ -51,8 +51,8 @@
           <attribute name="ClusterName">TreeCache-Cluster</attribute>
           
           <!--Uncomment next three statements to enable JGroups multiplexer.
  -              This configuration is dependent on the JGroups multiplexer being
  -              registered in an MBean server such as JBossAS.  -->
  +This configuration is dependent on the JGroups multiplexer being
  +registered in an MBean server such as JBossAS.  -->
           <!--
           <depends>jgroups.mux:name=Multiplexer</depends>
           <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
  @@ -140,7 +140,7 @@
   
                   <!-- the following three elements, all relating to data gravitation, default to false -->
                   <!-- Should data gravitation be attempted whenever there is a cache miss on finding a node?
  -                     If false, data will only be gravitated if an Option is set enabling it -->
  +If false, data will only be gravitated if an Option is set enabling it -->
                   <autoDataGravitation>false</autoDataGravitation>
                   <!-- removes data on remote caches' trees and backup subtrees when gravitated to a new data owner -->
                   <dataGravitationRemoveOnFind>true</dataGravitationRemoveOnFind>