[jboss-cvs] JBossAS SVN: r71074 - branches/JBPAPP_4_2_0_GA_CP/server/src/etc/deploy.

jboss-cvs-commits at lists.jboss.org jboss-cvs-commits at lists.jboss.org
Thu Mar 20 11:35:00 EDT 2008


Author: bstansberry at jboss.com
Date: 2008-03-20 11:35:00 -0400 (Thu, 20 Mar 2008)
New Revision: 71074

Modified:
   branches/JBPAPP_4_2_0_GA_CP/server/src/etc/deploy/cache-invalidation-service.xml
Log:
[JBPAPP-521] Update cache invalidation using jms bridge for jboss messaging

Modified: branches/JBPAPP_4_2_0_GA_CP/server/src/etc/deploy/cache-invalidation-service.xml
===================================================================
--- branches/JBPAPP_4_2_0_GA_CP/server/src/etc/deploy/cache-invalidation-service.xml	2008-03-20 15:34:43 UTC (rev 71073)
+++ branches/JBPAPP_4_2_0_GA_CP/server/src/etc/deploy/cache-invalidation-service.xml	2008-03-20 15:35:00 UTC (rev 71074)
@@ -16,8 +16,9 @@
 
 
 <!--
-	Uncomment if you want to activate the cache invalidation mechanism accross
-	nodes using the JMS bridge 
+	Uncomment one of the following two sets of beans if you want to 
+	activate the EJB2 entity cache invalidation mechanism across nodes 
+	using the JMS bridge.
 
 	PropagationMode can be : IN_OUT = 1, IN_ONLY = 2, OUT_ONLY = 3
 
@@ -27,22 +28,42 @@
       <attribute name="ProviderUrl">MyOtherNode:1099</attribute>
 
 -->
+<!-- Uncomment this pair of mbeans if you are using JBossMQ for JMS-based cache invalidation -->
 <!--
+  <mbean code="org.jboss.cache.invalidation.bridges.JMSCacheInvalidationBridge" 
+         name="jboss.cache:service=InvalidationBridge,type=JavaGroups">
+     <depends>jboss.cache:service=InvalidationManager</depends>
+     <depends>jboss.mq.destination:service=Topic,name=JMSCacheInvalidationBridge</depends>
+     <attribute name="InvalidationManager">jboss.cache:service=InvalidationManager</attribute>
+     <attribute name="ConnectionFactoryName">java:/ConnectionFactory</attribute>
+     <attribute name="TopicName">topic/JMSCacheInvalidationBridge</attribute>
+     <attribute name="PropagationMode">1</attribute> 
+  </mbean>
+  
   <mbean code="org.jboss.mq.server.jmx.Topic"
 	 name="jboss.mq.destination:service=Topic,name=JMSCacheInvalidationBridge">
     <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
     <depends optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager</depends>
   </mbean>
-
+-->
+<!--Uncomment this pair of mbeans if you are using JBoss Messaging for JMS-based cache invalidation -->
+<!--
   <mbean code="org.jboss.cache.invalidation.bridges.JMSCacheInvalidationBridge" 
          name="jboss.cache:service=InvalidationBridge,type=JavaGroups">
      <depends>jboss.cache:service=InvalidationManager</depends>
-     <depends>jboss.mq.destination:service=Topic,name=JMSCacheInvalidationBridge</depends>
+     <depends>jboss.messaging.destination:service=Topic,name=JMSCacheInvalidationBridge</depends>
      <attribute name="InvalidationManager">jboss.cache:service=InvalidationManager</attribute>
      <attribute name="ConnectionFactoryName">java:/ConnectionFactory</attribute>
      <attribute name="TopicName">topic/JMSCacheInvalidationBridge</attribute>
      <attribute name="PropagationMode">1</attribute> 
   </mbean>
+  
+  <mbean code="org.jboss.jms.server.destination.TopicService"
+	 name="jboss.messaging.destination:service=Topic,name=JMSCacheInvalidationBridge"
+	 xmbean-dd="xmdesc/Topic-xmbean.xml">
+	  <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
+      <depends>jboss.messaging:service=PostOffice</depends>
+  </mbean>
 -->
      
 </server>




More information about the jboss-cvs-commits mailing list