49 lines
2.1 KiB
XML
49 lines
2.1 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE server>
|
|
<!-- $Id: cache-invalidation-service.xml,v 1.1 2006/04/21 17:58:45 jjanke Exp $ -->
|
|
|
|
<!-- ===================================================================== -->
|
|
<!-- -->
|
|
<!-- Cache Invalidation Service -->
|
|
<!-- -->
|
|
<!-- ===================================================================== -->
|
|
|
|
<server>
|
|
|
|
<mbean code="org.jboss.cache.invalidation.InvalidationManager"
|
|
name="jboss.cache:service=InvalidationManager">
|
|
</mbean>
|
|
|
|
|
|
<!--
|
|
Uncomment if you want to activate the cache invalidation mechanism accross
|
|
nodes using the JMS bridge
|
|
|
|
PropagationMode can be : IN_OUT = 1, IN_ONLY = 2, OUT_ONLY = 3
|
|
|
|
You can also set the ProviderUrl attribute to another IP:port setting if you
|
|
must lookup your JMS information in other JMS trees i.e.
|
|
|
|
<attribute name="ProviderUrl">MyOtherNode:1099</attribute>
|
|
|
|
-->
|
|
<!--
|
|
<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>
|
|
|
|
<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>
|
|
-->
|
|
|
|
</server>
|