Shouldn't the element lie within the element
as in the example code ? We could thus have different listeners performing different
sequence of actions.
| <EsbConfig
command-queue-class="org.jboss.soa.esb.command.InMemoryCommandQueue"
| command-queue-name="test-queue"
| >
|
| <ListenerConfig
| listenerClass="org.jboss.soa.esb.util.MockPoller"
| actions="X12N837-to-HL7V3, Process-HL7V3-Claim, HL7V3-to-X12N837,
Route-to-Claims"
| maxThreads="1"
| >
|
| <Actions>
| <!--
| Under the new architecture I think these will be equivalent to "Contracts
Definitions"?
| -->
| <Action name="X12N837-to-HL7V3" processor="Smooks" />
| <Action name="Process-HL7V3-Claim"
processor="ClaimsProcessor" />
| <Action name="HL7V3-to-X12N837" processor="Smooks" />
| <Action name="Route-to-Claims" processor="SocketRouter">
| <property name="address" value="xxxxx" />
| </Action>
|
| <ProcessorAliases>
| <!--
| Under the new architecture I think these will be equivalent to
"Services"? The alias "name" being like the Service URN.
| -->
| <Alias name="Smooks"
class="org.jboss.soa.esb.actions.SmooksTransformActionProcessor" />
| <Alias name="ClaimsProcessor"
class="com.acme.health.ClaimsProcessor" />
| <Alias name="JmsRouter"
class="org.jboss.soa.esb.actions.JmsRouter" />
| <Alias name="SocketRouter"
class="org.jboss.soa.esb.actions.SocketRouter" />
| </ProcessorAliases>
| </Actions>
| </ListenerConfig>
|
| </EsbConfig>
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971054#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...