Show Table of Contents
10.6. Attributes of a Listener
The “base” <listener> possesses the following attributes. These attribute definitions are inherited by all <listener> extensions. As such, they can be set for all of the listeners and gateways supported by the JBoss Enterprise SOA Platform, such as InVM.
Table 10.2. Listener Attributes
| Name | Description | Type | Required |
|---|---|---|---|
| name | The name of the listener. This attribute is required primarily for logging purposes. | xsd:string | true |
| busrefid | Reference to the busid of the <bus> through which the listener instance receives messages. | xsd:string | true |
| maxThreads | The maximum number of concurrent message processing threads that the listener can have active. | xsd:int | True |
| is-gateway | Whether or not the listener instance is a “Gateway” or “Message Aware” Listener.
A message bus defines the details of a specific message channel or transport.
| xsd:boolean | true |
Listeners can define a set of zero or more <property> elements (just like the <provider> and <bus> elements/types). These are used to define listener specific properties.
Note
For each gateway listener defined in a service, an ESB-aware (or “native”) listener must also be defined. This is because gateway listeners do not define bidirectional endpoints but, rather, “start points” into the ESB. You cannot send a message to a gateway from within the ESB. Also, note that, since a gateway is not an endpoint, it does not have an Endpoint Reference (EPR) persisted in the registry.
Here is an example of a <listener> referencing a <bus>:
<?xml version = "1.0" encoding = "UTF-8"?>
<jbossesb xmlns="http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.3.0.xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.3.0.xsd http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.3.0.xsd"
parameterReloadSecs="5">
<providers>
<jms-provider name="JBossMQ" connection-factory="ConnectionFactory">
<jms-bus busid="Reconciliation">
<jms-message-filter
dest-type="QUEUE"
dest-name="queue/B"
/>
</jms-bus>
<!-- busid --> <jms-bus busid="ReconciliationEsb">
<jms-message-filter
dest-type="QUEUE"
dest-name="queue/C"
</jms-bus>
</jms-provider>
</providers>
<services>
<service category="Bank" name="Reconciliation"
description="Bank Reconciliation Service">
<listeners>
<!-- busidref --> <jms-listener name="Bank-Listener"
busidref="Reconciliation"
is-gateway="true"/>
<jms-listener name="Bank-Esb"
busidref="ReconciliationEsb"/>
</listeners>
<actions>
....
</actions>
</service>
</services>
</jbossesb>

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.