invmScope="GLOBAL"
1
. To add additional Endpoints for the Service, we need to explicitly
add listener configurations on the Service. JBossESB supports two forms of listener
configuration:
1. Gateway Listeners: These listener configurations configure a “Gateway” Endpoint.
These Endpoint types can be used to get messages onto an ESB bus. It is responsible
for “normalizing” the message payload by wrapping it into an ESB Message (see
below) before shipping it to the Service's Action Pipeline.
2. ESB Aware Listeners: These listener configurations configure an “ESB Aware”
Endpoint. These Endpoint types are used to exchange ESB Messages (see below)
between ESB Aware components e.g. exchanging messages on the bus.
The following is an example of how a JMS Gateway listener can be added to the above
ShoeStore Service.
<?xml version = "1.0" encoding = "UTF-8"?>
<jbossesb xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/
trunk/product/etc/schemas/xml/jbossesb-1.0.1.xsd">
<providers>
<jms-provider name="JBossMQ" connection-factory="ConnectionFactory">
<jms-bus busid="shoeStoreJMSGateway">
<jms-message-filter dest-type="QUEUE" dest-name="queue/shoeStoreJMSGateway"/>
</jms-bus>
</jms-provider>
</providers>
<services>
<service category="Retail" name="ShoeStore" description="Acme Shoe Store Service"
invmScope=”GLOBAL”>
<listeners>
<jms-listener name="shoeStoreJMSGateway" busidref="shoeStoreJMSGateway"
is-gateway="true"/>
</listeners>
<actions>
<action name="println" class="org.jboss.soa.esb.actions.SystemPrintln" />
</actions>
</service>
</services>
</jbossesb>
In the above configurat
ion,
we
added a b
us <prov
iders>
s
ection to the
configuration
. This
is
where we configure the transport level details for Endpoints. In this case we added a <jms-
provider> section that defines a single <jms-bus> for the Shoe Store JMS Queue. This bus is
then referenced in the <jms-listener> defined on the Shoe Store Service. The Shoe Store is
now invocable via two Endpoints – the InVM Endpoint and the JMS Gateway Endpoint. The
ServiceInvoker will always use a Service's local InVM Endpoint, if available, in preference to
other Endpoint types.
The Message
All interactions between clients and services within JBossESB occur through the exchange of
Messages. In order to encourage loose coupling we recommend a message-exchange pattern
based on one-way messages, i.e., requests and responses are independent messages, correlated
where necessary by the infrastructure or application. Applications constructed in this way are
less brittle and can be more tolerant of failures, giving developers more flexibility in their
deployment and message delivery requirements.
To ensure loose coupling of services and develop SOA applications, it is necessary to:
1
The InVM transport is a new feature since JBossESB 4.3 that provides communication
between services running on the same JVM. Section 4.3.3, "InVM Transport" contains more
information about this feature.
JBESB-PG-3/26/10 18
我的内容管理
展开
