[jboss-cvs] JBoss Messaging SVN: r6847 - in trunk: docs/user-manual/en and 2 other directories.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon May 18 12:26:09 EDT 2009
Author: ataylor
Date: 2009-05-18 12:26:09 -0400 (Mon, 18 May 2009)
New Revision: 6847
Added:
trunk/docs/user-manual/en/modules/configuration-index.xml
Modified:
trunk/docs/user-manual/en/master.xml
trunk/docs/user-manual/en/modules/configuring-transports.xml
trunk/docs/user-manual/en/modules/connection-ttl.xml
trunk/docs/user-manual/en/modules/duplicate-detection.xml
trunk/docs/user-manual/en/modules/ha.xml
trunk/docs/user-manual/en/modules/large-messages.xml
trunk/docs/user-manual/en/modules/management.xml
trunk/docs/user-manual/en/modules/message-expiry.xml
trunk/docs/user-manual/en/modules/persistence.xml
trunk/docs/user-manual/en/modules/queue-attributes.xml
trunk/docs/user-manual/en/modules/security.xml
trunk/docs/user-manual/en/modules/thread-pooling.xml
trunk/docs/user-manual/user-manual.xpr
trunk/src/config/common/schema/jbm-configuration.xsd
Log:
added server config reference
Modified: trunk/docs/user-manual/en/master.xml
===================================================================
--- trunk/docs/user-manual/en/master.xml 2009-05-18 15:30:06 UTC (rev 6846)
+++ trunk/docs/user-manual/en/master.xml 2009-05-18 16:26:09 UTC (rev 6847)
@@ -41,7 +41,8 @@
<!ENTITY clusters SYSTEM "modules/clusters.xml">
<!ENTITY ha SYSTEM "modules/ha.xml">
<!ENTITY interoperability SYSTEM "modules/interoperability.xml">
- <!ENTITY perf-tuning SYSTEM "modules/perf-tuning.xml">
+ <!ENTITY perf-tuning SYSTEM "modules/perf-tuning.xml">
+ <!ENTITY configuration-index SYSTEM "modules/configuration-index.xml">
]>
<book lang="en">
<bookinfo>
@@ -88,5 +89,6 @@
&ha;
&interoperability;
&perf-tuning;
+ &configuration-index;
</book>
Added: trunk/docs/user-manual/en/modules/configuration-index.xml
===================================================================
--- trunk/docs/user-manual/en/modules/configuration-index.xml (rev 0)
+++ trunk/docs/user-manual/en/modules/configuration-index.xml 2009-05-18 16:26:09 UTC (rev 6847)
@@ -0,0 +1,347 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="configuration-index">
+ <title>Server Configuration Reference</title>
+ <para>This section is a quick index for looking up configuration.</para>
+ <section>
+ <title>jbm-configuration.xml</title>
+ <table frame="border">
+ <title>Server Configuration</title>
+ <tgroup cols="3">
+ <colspec colname="c1" colnum="1"/>
+ <colspec colname="c2" colnum="2"/>
+ <colspec colname="c3" colnum="3"/>
+ <thead>
+ <row>
+ <entry>Element Name</entry>
+ <entry>Element Type</entry>
+ <entry>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>clustered</entry>
+ <entry>Boolean</entry>
+ <entry>True means that the server is clustered</entry>
+ </row>
+ <row>
+ <entry>enable-file-deployment</entry>
+ <entry>Boolean</entry>
+ <entry>True means that the server will load configuration from the
+ configuration files</entry>
+ </row>
+ <row>
+ <entry><link linkend="enable.persistence">enable-persistence</link></entry>
+ <entry>Boolean</entry>
+ <entry>True means that the server will use the file based journal for
+ persistence.</entry>
+ </row>
+ <row>
+ <entry><link linkend="server.scheduled.thread.pool"
+ >scheduled-thread-pool-max-size</link></entry>
+ <entry>Integer</entry>
+ <entry>The number of threads that the main scheduled thread pool
+ has.</entry>
+ </row>
+ <row>
+ <entry><link linkend="server.scheduled.thread.pool"
+ >thread-pool-max-size</link></entry>
+ <entry>Integer</entry>
+ <entry>The number of threads that the main thread pool has</entry>
+ </row>
+ <row>
+ <entry>security-enabled</entry>
+ <entry>Boolean</entry>
+ <entry>True means that security is enabled</entry>
+ </row>
+ <row>
+ <entry>security-invalidation-interval</entry>
+ <entry>Long</entry>
+ <entry>How long, in milli seconds, to wait before invalidating the security
+ cache</entry>
+ </row>
+ <row>
+ <entry>wild-card-routing-enabled</entry>
+ <entry>Boolean</entry>
+ <entry>True means that the server supports wild card routing</entry>
+ </row>
+ <row>
+ <entry><link linkend="management.core.configuration"
+ >management-address</link></entry>
+ <entry>String</entry>
+ <entry>The name of the management address to send management messages
+ too.</entry>
+ </row>
+ <row>
+ <entry><link linkend="management.notifications.core.configuration"
+ >management-notification-address</link></entry>
+ <entry>String</entry>
+ <entry>The name of the address that consumers bind to to receive management
+ notifications</entry>
+ </row>
+ <row>
+ <entry><link linkend="management.replication"
+ >management-cluster-password</link></entry>
+ <entry>String</entry>
+ <entry>The password used to for replicating management operations between
+ clustered nodes</entry>
+ </row>
+ <row>
+ <entry><link linkend="management.replication"
+ >management-request-timeout</link></entry>
+ <entry>Long</entry>
+ <entry>How long, in milli seconds, to wait for a reply to a management
+ request</entry>
+ </row>
+ <row>
+ <entry><link linkend="management.jmx.configuration"
+ >jmx-management-enabled</link></entry>
+ <entry>Boolean</entry>
+ <entry>True means that the management API is available via JMX</entry>
+ </row>
+ <row>
+ <entry><link linkend="configuring.message.counters"
+ >message-counter-enabled</link></entry>
+ <entry>Boolean</entry>
+ <entry>True means that message counters are enabled</entry>
+ </row>
+ <row>
+ <entry><link linkend="configuring.message.counters"
+ >message-counter-sample-period</link></entry>
+ <entry>Long</entry>
+ <entry>The sample period to use for message counters</entry>
+ </row>
+ <row>
+ <entry><link linkend="configuring.message.counters"
+ >message-counter-max-day-history</link></entry>
+ <entry>Integer</entry>
+ <entry>How many days to keep message counter history</entry>
+ </row>
+ <row>
+ <entry><link linkend="dead.connections"
+ >connection-scan-period</link></entry>
+ <entry>Long</entry>
+ <entry>How often, in milli seconds, to scan for failed connections on the
+ server </entry>
+ </row>
+ <row>
+ <entry><link linkend="dead.connections"
+ >connection-ttl-override</link></entry>
+ <entry>Long</entry>
+ <entry>If set, this will override how long to keep a connection alive
+ without receiving a ping. </entry>
+ </row>
+ <row>
+ <entry>transaction-timeout</entry>
+ <entry>Long</entry>
+ <entry>How long before a transaction can be removed from the resource
+ manager after create time</entry>
+ </row>
+ <row>
+ <entry>transaction-timeout-scan-period</entry>
+ <entry>Long</entry>
+ <entry>How often, in milli seconds, to scan for timeout transactions</entry>
+ </row>
+ <row>
+ <entry><link linkend="configuring.expiry.reaper"
+ >message-expiry-scan-period</link></entry>
+ <entry>Long</entry>
+ <entry>How often, in milli seconds, to scan for expired messages</entry>
+ </row>
+ <row>
+ <entry><link linkend="configuring.expiry.reaper"
+ >message-expiry-thread-priority</link></entry>
+ <entry>Integer</entry>
+ <entry>The priority of the thread expiring messages</entry>
+ </row>
+ <row>
+ <entry><link linkend="duplicate.id.cache">id-cache-size</link></entry>
+ <entry>Integer</entry>
+ <entry>The size of the cache for pre creating message id's</entry>
+ </row>
+ <row>
+ <entry><link linkend="duplicate.id.cache">persist-id-cache</link></entry>
+ <entry>Boolean</entry>
+ <entry>True means that id's are persisted to the journal</entry>
+ </row>
+ <row>
+ <entry><link linkend="queue.activation.timeout"
+ >queue-activation-timeout</link></entry>
+ <entry>Long</entry>
+ <entry>After failout occurs, this time specifies how long to wait for
+ consumers to re attach before commencing delivery</entry>
+ </row>
+ <row>
+ <entry><link linkend="configuring.live.backup">backup</link></entry>
+ <entry>Boolean</entry>
+ <entry>True means that this server is a back up to another node in the a
+ cluster</entry>
+ </row>
+ <row>
+ <entry>persist-delivery-count-before-delivery</entry>
+ <entry>Boolean</entry>
+ <entry>True means that the delivery count is persisted before delivery.
+ False means that this only happens after a message has been
+ cancelled.</entry>
+ </row>
+ <row>
+ <entry><link linkend="configuring.live.backup"
+ >backup-connector-ref</link></entry>
+ <entry>String</entry>
+ <entry>The name of the remoting connector to use for the backup node
+ when.</entry>
+ </row>
+ <row>
+ <entry><link linkend="paging.main.config">paging-directory</link></entry>
+ <entry>String</entry>
+ <entry>The directory to store paged messages in</entry>
+ </row>
+ <row>
+ <entry><link linkend="paging.main.config"
+ >paging-global-watermark-size</link></entry>
+ <entry>Long</entry>
+ <entry>JBoss Messaging enters into global page mode as soon as the total
+ memory consumed by messages hits this value</entry>
+ </row>
+ <row>
+ <entry><link linkend="paging.main.config"
+ >paging-max-global-size-bytes</link></entry>
+ <entry>Long</entry>
+ <entry>The watermark used to determine when we start depaging</entry>
+ </row>
+ <row>
+ <entry><link linkend="configuring.bindings.journal"
+ >bindings-directory</link></entry>
+ <entry>String</entry>
+ <entry>The directory to store the persisted bindings to</entry>
+ </row>
+ <row>
+ <entry><link linkend="configuring.bindings.journal"
+ >create-bindings-dir</link></entry>
+ <entry>Boolean</entry>
+ <entry>True means that the server will create the bindings directory on
+ start up</entry>
+ </row>
+ <row>
+ <entry><link linkend="configuring.message.journal"
+ >journal-directory</link></entry>
+ <entry>String</entry>
+ <entry>The directory to store the journal files in</entry>
+ </row>
+ <row>
+ <entry><link linkend="configuring.message.journal"
+ >create-journal-dir</link></entry>
+ <entry>Boolean</entry>
+ <entry>True means that the journal directory will be created</entry>
+ </row>
+ <row>
+ <entry><link linkend="configuring.message.journal"
+ >journal-type</link></entry>
+ <entry>ASYNCIO|NIO</entry>
+ <entry>What type of journal to use</entry>
+ </row>
+ <row>
+ <entry><link linkend="configuring.message.journal"
+ >journal-buffer-reuse-size</link></entry>
+ <entry>Long</entry>
+ <entry>The journal will try and re use any buffers smaller than this
+ size.</entry>
+ </row>
+ <row>
+ <entry><link linkend="configuring.message.journal"
+ >journal-sync-transactional</link></entry>
+ <entry>Boolean</entry>
+ <entry>If true wait for transaction data to be synced to the journal before
+ returning response to client.</entry>
+ </row>
+ <row>
+ <entry><link linkend="configuring.message.journal"
+ >journal-sync-non-transactional</link></entry>
+ <entry>Boolean</entry>
+ <entry>If true wait for non transaction data to be synced to the journal
+ before returning response to client.</entry>
+ </row>
+ <row>
+ <entry><link linkend="configuring.message.journal"
+ >journal-file-size</link></entry>
+ <entry>Long</entry>
+ <entry>The max size, in bytes, each journal file should be</entry>
+ </row>
+ <row>
+ <entry><link linkend="configuring.message.journal"
+ >journal-min-files</link></entry>
+ <entry>Integer</entry>
+ <entry>How many journal files to pre create</entry>
+ </row>
+ <row>
+ <entry><link linkend="configuring.message.journal"
+ >journal-max-aio</link></entry>
+ <entry>Integer</entry>
+ <entry>The maximum number of write requests that can be in the AIO queue at
+ any one time</entry>
+ </row>
+ <row>
+ <entry><link linkend="large.message.configuring"
+ >large-messages-directory</link></entry>
+ <entry>String</entry>
+ <entry>The directory to store large messages</entry>
+ </row>
+ <row>
+ <entry><link linkend="understanding.connectors">connectors</link></entry>
+ <entry>Connector</entry>
+ <entry>A list of remoting connectors configurations to create</entry>
+ </row>
+ <row>
+ <entry><link linkend="configuring-transports.acceptors"
+ >acceptors</link></entry>
+ <entry>Acceptor</entry>
+ <entry>A list of remoting acceptors to create</entry>
+ </row>
+ <row>
+ <entry><link linkend="clusters.broadcast-groups"
+ >broadcast-groups</link></entry>
+ <entry>BroadcastGroup</entry>
+ <entry>A list of broadcast groups to create</entry>
+ </row>
+ <row>
+ <entry><link linkend="discoverclusters.discovery-groups"
+ >discovery-groups</link></entry>
+ <entry>DiscoveryGroup</entry>
+ <entry>A list of discovery groups to create</entry>
+ </row>
+ <row>
+ <entry><link linkend="diverts">diverts</link></entry>
+ <entry>Divert</entry>
+ <entry>A list of diverts to use</entry>
+ </row>
+ <row>
+ <entry><link linkend="predefined.queues">queues</link></entry>
+ <entry>Queue</entry>
+ <entry>A list of pre configured queues to create</entry>
+ </row>
+ <row>
+ <entry><link linkend="core-bridges">bridges</link></entry>
+ <entry>Bridge</entry>
+ <entry>A list of bridges to create</entry>
+ </row>
+ <row>
+ <entry><link linkend="clusters.cluster-connections"
+ >cluster-connections</link></entry>
+ <entry>ClusterConnection</entry>
+ <entry>A list of cluster connections</entry>
+ </row>
+ <row>
+ <entry><link linkend="security.settings.roles"
+ >security-settings</link></entry>
+ <entry>SecuritySetting</entry>
+ <entry>A list of security settings</entry>
+ </row>
+ <row>
+ <entry>address-settings</entry>
+ <entry>AddressSetting</entry>
+ <entry>A list of address settings</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </section>
+</chapter>
Modified: trunk/docs/user-manual/en/modules/configuring-transports.xml
===================================================================
--- trunk/docs/user-manual/en/modules/configuring-transports.xml 2009-05-18 15:30:06 UTC (rev 6846)
+++ trunk/docs/user-manual/en/modules/configuring-transports.xml 2009-05-18 16:26:09 UTC (rev 6847)
@@ -43,7 +43,7 @@
<para>Keys are always strings and values can be of type Long, Integer, String or
Boolean.</para>
</section>
- <section>
+ <section id="understanding.connectors">
<title>Understanding Connectors</title>
<para>Whereas acceptors are used on the server to define how we accept connections,
connectors are used by a client to define how it connects to a server.</para>
Modified: trunk/docs/user-manual/en/modules/connection-ttl.xml
===================================================================
--- trunk/docs/user-manual/en/modules/connection-ttl.xml 2009-05-18 15:30:06 UTC (rev 6846)
+++ trunk/docs/user-manual/en/modules/connection-ttl.xml 2009-05-18 16:26:09 UTC (rev 6847)
@@ -4,7 +4,7 @@
<para>In this section we will discuss connection time-to-live (TTL) and explain how JBoss
Messaging deals with crashed clients and clients which have exited without cleanly closing
their resources. We'll also explain how to configure all the related parameters.</para>
- <section>
+ <section id="dead.connections">
<title>Cleaning up Dead Connection Resources on the Server</title>
<para>Before a JBoss Messaging client application exits it is considered good practice and
part of its contract that it should close its resources in a controlled manager, using a
Modified: trunk/docs/user-manual/en/modules/duplicate-detection.xml
===================================================================
--- trunk/docs/user-manual/en/modules/duplicate-detection.xml 2009-05-18 15:30:06 UTC (rev 6846)
+++ trunk/docs/user-manual/en/modules/duplicate-detection.xml 2009-05-18 16:26:09 UTC (rev 6847)
@@ -76,7 +76,7 @@
...
</programlisting>
</section>
- <section>
+ <section id="duplicate.id.cache">
<title>Configuring the Duplicate ID Cache</title>
<para>The server maintains caches of received values of the <literal
>org.jboss.messaging.core.message.impl.HDR_DUPLICATE_DETECTION_ID</literal> property
Modified: trunk/docs/user-manual/en/modules/ha.xml
===================================================================
--- trunk/docs/user-manual/en/modules/ha.xml 2009-05-18 15:30:06 UTC (rev 6846)
+++ trunk/docs/user-manual/en/modules/ha.xml 2009-05-18 16:26:09 UTC (rev 6847)
@@ -28,7 +28,7 @@
replications in separate streams allows replication throughput to be much higher than if
we synchronously replicated data and waited for a response serially in an RPC manner
before replicating the next piece of data.</para>
- <section>
+ <section id="configuring.live.backup">
<title>Configuring live-backup pairs</title>
<para>First, on the live server, in <literal>jbm-configuration.xml</literal> configure
the live server with knowledge of its backup server. This is done by specifying a
@@ -83,7 +83,7 @@
to copy the entire server side configuration from live to backup and just make the
changes as specified in the previous section. </para>
</section>
- <section>
+ <section id="queue.activation.timeout">
<title>Queue activation timeout</title>
<para>If a live server fails, as client connections failover from the live node to the
backup, they do so at a rate determined by the client, and it might be the case that
Modified: trunk/docs/user-manual/en/modules/large-messages.xml
===================================================================
--- trunk/docs/user-manual/en/modules/large-messages.xml 2009-05-18 15:30:06 UTC (rev 6846)
+++ trunk/docs/user-manual/en/modules/large-messages.xml 2009-05-18 16:26:09 UTC (rev 6847)
@@ -9,7 +9,7 @@
transmission process, so it is possible to send and receive very large messages. </para>
<para>For example, it is possible to send an 8GB message even if you only had 50MB of RAM on
either client and server. </para>
- <section>
+ <section id="large.message.configuring">
<title>Configuring the server</title>
<para>Large messages are stored on a disk folder on the server side, as configured on the
main configuration file (<xref linkend="usingserver.mainconfig"/>)</para>
Modified: trunk/docs/user-manual/en/modules/management.xml
===================================================================
--- trunk/docs/user-manual/en/modules/management.xml 2009-05-18 15:30:06 UTC (rev 6846)
+++ trunk/docs/user-manual/en/modules/management.xml 2009-05-18 16:26:09 UTC (rev 6847)
@@ -379,7 +379,7 @@
</section>
</section>
- <section>
+ <section id="management.replication">
<title>Management Replication</title>
<para>JBoss Messaging allows to <emphasis>replicate</emphasis> a live server on a backup server.
This impacts management as resources created on the live server (e.g. a core address)
@@ -548,7 +548,7 @@
</listitem>
</itemizedlist>
- <section>
+ <section id="configuring.message.counters">
<title>Configuring Message Counters</title>
<para>By default, message counters are disabled has it consumes memory (the metrics are kept in memory)
and CPU (the queues are sampled at regular interval).</para>
Modified: trunk/docs/user-manual/en/modules/message-expiry.xml
===================================================================
--- trunk/docs/user-manual/en/modules/message-expiry.xml 2009-05-18 15:30:06 UTC (rev 6846)
+++ trunk/docs/user-manual/en/modules/message-expiry.xml 2009-05-18 16:26:09 UTC (rev 6847)
@@ -47,7 +47,7 @@
from the queue. Address wildcards can be used
to configure expiry address for a set of addresses (see <xref linkend="wildcard-syntax" />).</para>
</section>
- <section>
+ <section id="configuring.expiry.reaper">
<title>Configuring The Expiry Reaper Thread</title>
<para>A reaper thread is periodically inspecting the queues to check if messages have
expired.</para>
Modified: trunk/docs/user-manual/en/modules/persistence.xml
===================================================================
--- trunk/docs/user-manual/en/modules/persistence.xml 2009-05-18 15:30:06 UTC (rev 6846)
+++ trunk/docs/user-manual/en/modules/persistence.xml 2009-05-18 16:26:09 UTC (rev 6847)
@@ -81,7 +81,7 @@
the chapter on paging [LINK]</para>
<para>If no persistence is required at all, JBoss Messaging can also be configured not to
persist any data at all to storage.</para>
- <section>
+ <section id="configuring.bindings.journal">
<title>Configuring the bindings journal</title>
<para>The bindings journal is configured using the following attributes in <literal
>jbm-configuration.xml</literal></para>
@@ -100,7 +100,7 @@
</listitem>
</itemizedlist>
</section>
- <section>
+ <section id="configuring.message.journal">
<title>Configuring the message journal</title>
<para>The message journal is configured using the following attributes in <literal
>jbm-configuration.xml</literal></para>
@@ -199,7 +199,7 @@
<para>Using aptitude, (e.g. on Ubuntu or Debian system):
<programlisting>sudo apt-get install libaio1</programlisting></para>
</section>
- <section>
+ <section id="enable.persistence">
<title>Configuring JBoss Messaging for zero persistence</title>
<para> In some situations, zero persistence is sometimes required for a messaging system.
Configuring JBoss Messaging to perform zero persistence is straightforward. Simply set
Modified: trunk/docs/user-manual/en/modules/queue-attributes.xml
===================================================================
--- trunk/docs/user-manual/en/modules/queue-attributes.xml 2009-05-18 15:30:06 UTC (rev 6846)
+++ trunk/docs/user-manual/en/modules/queue-attributes.xml 2009-05-18 16:26:09 UTC (rev 6847)
@@ -4,7 +4,7 @@
<para>Queue attributes can be set in one of 2 ways. Either by configuring them via the
configuration file or when using the core API. This chapter will explain how to configure
each attribute and what effect the attribute has.</para>
- <section>
+ <section id="predefined.queues">
<title>Predefined Queues</title>
<para>Queues can be predefined via configuration at a core level or at a JMS level. Firstly
lets look at a JMS level.</para>
Modified: trunk/docs/user-manual/en/modules/security.xml
===================================================================
--- trunk/docs/user-manual/en/modules/security.xml 2009-05-18 15:30:06 UTC (rev 6846)
+++ trunk/docs/user-manual/en/modules/security.xml 2009-05-18 16:26:09 UTC (rev 6847)
@@ -3,7 +3,7 @@
<title>Security</title>
<para>This chapter describes how security works with JBoss Messaging and how you can configure
it.</para>
- <section>
+ <section id="security.settings.roles">
<title>Role based security for addresses</title>
<para>JBoss Messaging contains a flexible role-based security model for applying security to
queues, based on their addresses.</para>
Modified: trunk/docs/user-manual/en/modules/thread-pooling.xml
===================================================================
--- trunk/docs/user-manual/en/modules/thread-pooling.xml 2009-05-18 15:30:06 UTC (rev 6846)
+++ trunk/docs/user-manual/en/modules/thread-pooling.xml 2009-05-18 16:26:09 UTC (rev 6847)
@@ -13,7 +13,7 @@
for both scheduled and non scheduled activity.</para>
<para>There are also a small number of other places where threads are used directly, we'll
discuss each in turn.</para>
- <section>
+ <section id="server.scheduled.thread.pool">
<title>Server Scheduled Thread Pool</title>
<para>The server scheduled thread pool is used for most activities on the server side
that require running periodically or with delays. It maps internally to a <literal
Modified: trunk/docs/user-manual/user-manual.xpr
===================================================================
--- trunk/docs/user-manual/user-manual.xpr 2009-05-18 15:30:06 UTC (rev 6846)
+++ trunk/docs/user-manual/user-manual.xpr 2009-05-18 16:26:09 UTC (rev 6847)
@@ -13,6 +13,7 @@
<file name="en/modules/architecture.xml"/>
<file name="en/modules/client-reconnection.xml"/>
<file name="en/modules/clusters.xml"/>
+ <file name="en/modules/configuration-index.xml"/>
<file name="en/modules/configuring-transports.xml"/>
<file name="en/modules/connection-ttl.xml"/>
<file name="en/modules/core-bridges.xml"/>
Modified: trunk/src/config/common/schema/jbm-configuration.xsd
===================================================================
--- trunk/src/config/common/schema/jbm-configuration.xsd 2009-05-18 15:30:06 UTC (rev 6846)
+++ trunk/src/config/common/schema/jbm-configuration.xsd 2009-05-18 16:26:09 UTC (rev 6847)
@@ -98,10 +98,7 @@
</xsd:element>
<xsd:element name="persist-delivery-count-before-delivery" type="xsd:boolean"
maxOccurs="1" minOccurs="0">
- </xsd:element>
- <xsd:element name="allow-route-when-no-bindings" type="xsd:boolean"
- maxOccurs="1" minOccurs="0">
- </xsd:element>
+ </xsd:element>
<xsd:element name="backup-connector-ref"
type="backup-connectorType" maxOccurs="1" minOccurs="0">
</xsd:element>
@@ -168,9 +165,6 @@
</xsd:sequence>
</xsd:complexType>
</xsd:element>
- <xsd:element name="paging-max-threads" type="xsd:positiveInteger"
- maxOccurs="1" minOccurs="0">
- </xsd:element>
<xsd:element name="paging-directory" type="xsd:string"
maxOccurs="1" minOccurs="0">
</xsd:element>
More information about the jboss-cvs-commits
mailing list