[jboss-dev-forums] [JBoss ESB Development] New message: "Re: Smooks problem"

Gilles Dupont Tagne Tagne do-not-reply at jboss.com
Wed Jan 13 06:34:24 EST 2010


JBoss development,

A new message was posted in the thread "Smooks problem":

http://community.jboss.org/message/519788#519788

Author  : Gilles Dupont Tagne Tagne
Profile : http://community.jboss.org/people/tagnegilles

Message:
--------------------------------------------------------------
splitter-ds.xml
<?xml version="1.0" encoding="UTF-8"?>
<datasources>
   <local-tx-datasource>
      <jndi-name>SplitterSqlDB</jndi-name>
      <connection-url>jdbc:hsqldb:hsql://localhost:1704</connection-url>
      <driver-class>org.hsqldb.jdbcDriver</driver-class>
      <user-name>sa</user-name>
      <password></password>
      <min-pool-size>5</min-pool-size>
      <max-pool-size>20</max-pool-size>
      <idle-timeout-minutes>0</idle-timeout-minutes>
      <depends>jboss:service=SplitterSqlDB</depends>     
      <prepared-statement-cache-size>32</prepared-statement-cache-size>
   </local-tx-datasource>

   <mbean code="org.jboss.internal.soa.esb.dependencies.HypersonicDatabase"
     name="jboss:service=SplitterSqlDB">
     <attribute name="Port">1704</attribute>
     <attribute name="BindAddress">localhost</attribute> 
     <attribute name="Database">SplitterSqlDB</attribute>
     <attribute name="Silent">true</attribute>
     <attribute name="Trace">false</attribute>
     <attribute name="No_system_exit">true</attribute>
     <attribute name="DataDir">${jboss.server.data.dir}</attribute>
   </mbean>
</datasources>


 
myEsbmq-service.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE server PUBLIC -//JBoss//DTD MBean Service 5.0//EN http://www.jboss.org/j2ee/dtd/jboss-service_5_0.dtd >
<server>
    <mbean code="org.jboss.jms.server.destination.QueueService"
           name="jboss.esb.splitter:service=Queue,name=splitterQueue"
           xmbean-dd="xmdesc/Queue-xmbean.xml">
        <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
        <depends>jboss.messaging:service=PostOffice</depends>
    </mbean>
    
    <mbean code="org.jboss.jms.server.destination.QueueService"
           name="jboss.esb.splitter:service=Queue,name=splitterAgeESBQueue"
           xmbean-dd="xmdesc/Queue-xmbean.xml">
        <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
        <depends>jboss.messaging:service=PostOffice</depends>
    </mbean>    
 
     <mbean code="org.jboss.jms.server.bridge.BridgeService" name="splitter:service=Bridge,name=SplitterAgeBridge"
          xmbean-dd="xmdesc/Bridge-xmbean.xml">

          <!-- The JNDI lookup for the source destination -->
          <attribute name="SourceDestinationLookup">/queue/splitterAgeESBQueue</attribute>

          <!-- The JNDI lookup for the target destination -->
          <attribute name="TargetDestinationLookup">/queue/splitterAgeQueue</attribute>

          <!--
               The username to use for the source connection <attribute
               name="SourceUsername">bob</attribute>
          -->

          <!--
               The password to use for the source connection <attribute
               name="SourcePassword">cheesecake</attribute>
          -->

          <!--
               The username to use for the target connection <attribute
               name="TargetUsername">mary</attribute>
          -->

          <!--
               The password to use for the target connection <attribute
               name="TargetPassword">hotdog</attribute>
          -->

          <!--
               Optional: The Quality Of Service mode to use, one of:
               QOS_AT_MOST_ONCE = 0; QOS_DUPLICATES_OK = 1; QOS_ONCE_AND_ONLY_ONCE =
               2;
          -->
          <attribute name="QualityOfServiceMode">0</attribute>

          <!--
               JMS selector to use for consuming messages from the source <attribute
               name="Selector">specify jms selector here</attribute>
          -->

          <!--
               The maximum number of messages to consume from the source before
               sending to the target
          -->
          <attribute name="MaxBatchSize">1</attribute>

          <!--
               The maximum time to wait (in ms) before sending a batch to the target
               even if MaxBatchSize is not exceeded. -1 means wait forever
          -->
          <attribute name="MaxBatchTime">-1</attribute>

          <!--
               If consuming from a durable subscription this is the subscription
               name <attribute name="SubName">mysub</attribute>
          -->

          <!--
               If consuming from a durable subscription this is the client ID to use
               <attribute name="ClientID">myClientID</attribute>
          -->

          <!--
               The number of ms to wait between connection retrues in the event
               connections to source or target fail
          -->
          <attribute name="FailureRetryInterval">5000</attribute>

          <!--
               The maximum number of connection retries to make in case of failure,
               before giving up -1 means try forever
          -->
          <attribute name="MaxRetries">-1</attribute>

          <!--
               If true then the message id of the message before bridging will be
               added as a header to the message so it is available to the receiver.
               Can then be sent as correlation id to correlate in a distributed
               request-response
          -->
          <attribute name="AddMessageIDInHeader">false</attribute>
          
          <!--
               The JMS provider loader that is used to lookup the source destination
          -->
          <depends optional-attribute-name="SourceProviderLoader">
               jboss.messaging:service=JMSProviderLoader,name=JMSProvider</depends>

          <!--
               The JMS provider loader that is used to lookup the target destination
          -->
          <depends optional-attribute-name="TargetProviderLoader">
               jboss.messaging:service=JMSProviderLoader,name=JMSProvider</depends>
               
          <depends>jboss.esb.splitter:service=Queue,name=splitterAgeESBQueue</depends>
     </mbean>   
    
     <mbean code="org.jboss.jms.server.bridge.BridgeService" name="splitter:service=Bridge,name=SplitterBridge"
          xmbean-dd="xmdesc/Bridge-xmbean.xml">

          <!-- The JNDI lookup for the source destination -->
          <attribute name="SourceDestinationLookup">/queue/splitterQueue</attribute>

          <!-- The JNDI lookup for the target destination -->
          <attribute name="TargetDestinationLookup">/queue/splitterMDQueue</attribute>

          <!--
               The username to use for the source connection <attribute
               name="SourceUsername">bob</attribute>
          -->

          <!--
               The password to use for the source connection <attribute
               name="SourcePassword">cheesecake</attribute>
          -->

          <!--
               The username to use for the target connection <attribute
               name="TargetUsername">mary</attribute>
          -->

          <!--
               The password to use for the target connection <attribute
               name="TargetPassword">hotdog</attribute>
          -->

          <!--
               Optional: The Quality Of Service mode to use, one of:
               QOS_AT_MOST_ONCE = 0; QOS_DUPLICATES_OK = 1; QOS_ONCE_AND_ONLY_ONCE =
               2;
          -->
          <attribute name="QualityOfServiceMode">0</attribute>

          <!--
               JMS selector to use for consuming messages from the source <attribute
               name="Selector">specify jms selector here</attribute>
          -->

          <!--
               The maximum number of messages to consume from the source before
               sending to the target
          -->
          <attribute name="MaxBatchSize">1</attribute>

          <!--
               The maximum time to wait (in ms) before sending a batch to the target
               even if MaxBatchSize is not exceeded. -1 means wait forever
          -->
          <attribute name="MaxBatchTime">-1</attribute>

          <!--
               If consuming from a durable subscription this is the subscription
               name <attribute name="SubName">mysub</attribute>
          -->

          <!--
               If consuming from a durable subscription this is the client ID to use
               <attribute name="ClientID">myClientID</attribute>
          -->

          <!--
               The number of ms to wait between connection retrues in the event
               connections to source or target fail
          -->
          <attribute name="FailureRetryInterval">5000</attribute>

          <!--
               The maximum number of connection retries to make in case of failure,
               before giving up -1 means try forever
          -->
          <attribute name="MaxRetries">-1</attribute>

          <!--
               If true then the message id of the message before bridging will be
               added as a header to the message so it is available to the receiver.
               Can then be sent as correlation id to correlate in a distributed
               request-response
          -->
          <attribute name="AddMessageIDInHeader">false</attribute>
          
          <!--
               The JMS provider loader that is used to lookup the source destination
          -->
          <depends optional-attribute-name="SourceProviderLoader">
               jboss.messaging:service=JMSProviderLoader,name=JMSProvider</depends>

          <!--
               The JMS provider loader that is used to lookup the target destination
          -->
          <depends optional-attribute-name="TargetProviderLoader">
               jboss.messaging:service=JMSProviderLoader,name=JMSProvider</depends>
               
          <depends>jboss.esb.splitter:service=Queue,name=splitterQueue</depends>
     </mbean>    
</server>



--------------------------------------------------------------

To reply to this message visit the message page: http://community.jboss.org/message/519788#519788




More information about the jboss-dev-forums mailing list