[jboss-cvs] JBoss Messaging SVN: r7862 - in branches/JBMESSAGING-1742/integration: EAP4/etc/xmdesc and 1 other directory.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Oct 22 02:37:35 EDT 2009
Author: gaohoward
Date: 2009-10-22 02:37:35 -0400 (Thu, 22 Oct 2009)
New Revision: 7862
Modified:
branches/JBMESSAGING-1742/integration/AS5/etc/xmdesc/Queue-xmbean.xml
branches/JBMESSAGING-1742/integration/AS5/etc/xmdesc/Topic-xmbean.xml
branches/JBMESSAGING-1742/integration/EAP4/etc/xmdesc/Queue-xmbean.xml
branches/JBMESSAGING-1742/integration/EAP4/etc/xmdesc/Topic-xmbean.xml
Log:
add DropOldMessageOnRedeploy attribute
Modified: branches/JBMESSAGING-1742/integration/AS5/etc/xmdesc/Queue-xmbean.xml
===================================================================
--- branches/JBMESSAGING-1742/integration/AS5/etc/xmdesc/Queue-xmbean.xml 2009-10-21 10:03:19 UTC (rev 7861)
+++ branches/JBMESSAGING-1742/integration/AS5/etc/xmdesc/Queue-xmbean.xml 2009-10-22 06:37:35 UTC (rev 7862)
@@ -127,8 +127,14 @@
<description>Is this a clustered destination?</description>
<name>Clustered</name>
<type>boolean</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="isDropOldMessageOnRedeploy" setMethod="setDropOldMessageOnRedeploy">
+ <description>When you redeploy a queue after changing its clustered state, do you want to keep or abandon its existing messages?</description>
+ <name>DropOldMessageOnRedeploy</name>
+ <type>boolean</type>
</attribute>
-
+
<attribute access="read-only" getMethod="getMessageCounter">
<description>Get the message counter for the queue</description>
<name>MessageCounter</name>
Modified: branches/JBMESSAGING-1742/integration/AS5/etc/xmdesc/Topic-xmbean.xml
===================================================================
--- branches/JBMESSAGING-1742/integration/AS5/etc/xmdesc/Topic-xmbean.xml 2009-10-21 10:03:19 UTC (rev 7861)
+++ branches/JBMESSAGING-1742/integration/AS5/etc/xmdesc/Topic-xmbean.xml 2009-10-22 06:37:35 UTC (rev 7862)
@@ -109,6 +109,12 @@
<type>boolean</type>
</attribute>
+ <attribute access="read-write" getMethod="isDropOldMessageOnRedeploy" setMethod="setDropOldMessageOnRedeploy">
+ <description>When you redeploy a topic after changing its clustered state, do you want to keep or abandon its existing messages?</description>
+ <name>DropOldMessageOnRedeploy</name>
+ <type>boolean</type>
+ </attribute>
+
<attribute access="read-write" getMethod="getMessageCounterHistoryDayLimit" setMethod="setMessageCounterHistoryDayLimit">
<description>The day limit for the message counters of this topic</description>
<name>MessageCounterHistoryDayLimit</name>
Modified: branches/JBMESSAGING-1742/integration/EAP4/etc/xmdesc/Queue-xmbean.xml
===================================================================
--- branches/JBMESSAGING-1742/integration/EAP4/etc/xmdesc/Queue-xmbean.xml 2009-10-21 10:03:19 UTC (rev 7861)
+++ branches/JBMESSAGING-1742/integration/EAP4/etc/xmdesc/Queue-xmbean.xml 2009-10-22 06:37:35 UTC (rev 7862)
@@ -129,6 +129,12 @@
<type>boolean</type>
</attribute>
+ <attribute access="read-write" getMethod="isDropOldMessageOnRedeploy" setMethod="setDropOldMessageOnRedeploy">
+ <description>When you redeploy a queue after changing its clustered state, do you want to keep or abandon its existing messages?</description>
+ <name>DropOldMessageOnRedeploy</name>
+ <type>boolean</type>
+ </attribute>
+
<attribute access="read-only" getMethod="getMessageCounter">
<description>Get the message counter for the queue</description>
<name>MessageCounter</name>
Modified: branches/JBMESSAGING-1742/integration/EAP4/etc/xmdesc/Topic-xmbean.xml
===================================================================
--- branches/JBMESSAGING-1742/integration/EAP4/etc/xmdesc/Topic-xmbean.xml 2009-10-21 10:03:19 UTC (rev 7861)
+++ branches/JBMESSAGING-1742/integration/EAP4/etc/xmdesc/Topic-xmbean.xml 2009-10-22 06:37:35 UTC (rev 7862)
@@ -109,6 +109,12 @@
<type>boolean</type>
</attribute>
+ <attribute access="read-write" getMethod="isDropOldMessageOnRedeploy" setMethod="setDropOldMessageOnRedeploy">
+ <description>When you redeploy a topic after changing its clustered state, do you want to keep or abandon its existing messages?</description>
+ <name>DropOldMessageOnRedeploy</name>
+ <type>boolean</type>
+ </attribute>
+
<attribute access="read-write" getMethod="getMessageCounterHistoryDayLimit" setMethod="setMessageCounterHistoryDayLimit">
<description>The day limit for the message counters of this topic</description>
<name>MessageCounterHistoryDayLimit</name>
More information about the jboss-cvs-commits
mailing list