Return-Path: Delivered-To: apmail-cxf-dev-archive@www.apache.org Received: (qmail 22829 invoked from network); 27 Oct 2010 07:05:15 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 27 Oct 2010 07:05:15 -0000 Received: (qmail 14194 invoked by uid 500); 27 Oct 2010 07:05:15 -0000 Delivered-To: apmail-cxf-dev-archive@cxf.apache.org Received: (qmail 13970 invoked by uid 500); 27 Oct 2010 07:05:12 -0000 Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list dev@cxf.apache.org Received: (qmail 13962 invoked by uid 99); 27 Oct 2010 07:05:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Oct 2010 07:05:10 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [62.75.158.78] (HELO mail.liquid-reality.de) (62.75.158.78) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Oct 2010 07:05:03 +0000 Received: from [10.0.0.100] (HSI-KBW-091-089-018-199.hsi2.kabelbw.de [91.89.18.199]) by mail.liquid-reality.de (Postfix) with ESMTP id A5F79B38004 for ; Wed, 27 Oct 2010 07:04:42 +0000 (UTC) Message-ID: <4CC7CF06.5080207@die-schneider.net> Date: Wed, 27 Oct 2010 09:04:38 +0200 From: Christian Schneider User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.2.11) Gecko/20101013 Lightning/1.0b2 Thunderbird/3.1.5 MIME-Version: 1.0 To: dev@cxf.apache.org Subject: Re: Fwd: [CONF] Apache CXF Documentation > Using the JMSConfigFeature References: <16528185.2661.1288084680017.JavaMail.confluence@thor> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi Benson, I just checked the source code of jms transport. It seems that the is not even a property useMessageIDAsCorrealationID in JmsConfiguration. The JmsOldConfigHolder does not read this property. So this does not seem to be used at all. I just copied the description to the JmsConfigFeature as I assumed it should be present. I have not yet tested this with a Tibco Business Works Server where the messageId is used to correlate messages but I guess there could be problems. There could be another algorithm present of course. Any ideas? Best Regards Christian Am 26.10.2010 15:21, schrieb Benson Margulies: > There's a nasty spelling error highlighted here. Anyone care to open a JIRA? > > ---------- Forwarded message ---------- > From: > Date: Tue, Oct 26, 2010 at 5:18 AM > Subject: [CONF] Apache CXF Documentation> Using the JMSConfigFeature > To: commits@cxf.apache.org > > > Using the JMSConfigFeature > Page > *edited* by Christian > Schneider > Changes (1) > ... > true means use topics \\ | > | jmsProviderTibcoEms | false | true means that the jms provider is Tibco > EMS. Currently this activates that the principal in the SecurityContext is > populated from the header JMS_TIBCO_SENDER. (available from cxf version > 2.2.6) | > | useMessageIDAsCorrealationID | false | Specifies whether the JMS broker > will use the message ID to correlate messages. By default a CXF client will > set a generated correlation id instead | > \\ > Full Content > > In older CXF version the JMS transport is configured by defining a > JMSConduit or JMSDestination. Starting with CXF 2.0.9 and 2.1.3 the JMS > transport includes an easier configuration option that is more conformant to > the spring dependency injection. Additionally the new configuration has much > more options. For example it is not necessary anymore to use JNDI to resolve > the connection factory. Instead it can be defined in the spring config. > > The following example configs use the > p-namespacefrom > spring 2.5 but the old spring bean style is also possible. > > Inside a features element the JMSConfigFeature can be defined. > > xmlns:customer="http://customerservice.example.com/" serviceName="customer:CustomerServiceService" > endpointName="customer:CustomerServiceEndpoint" > address="jms://" serviceClass="com.example.customerservice.CustomerService"> > > p:jmsConfig-ref="jmsConfig"/> > > > > In the above example it references a bean "jmsConfig" where the whole > configuration for the JMS transport can be done. > > A jaxws Endpoint can be defined in the same way: > > xmlns:customer="http://customerservice.example.com/" id="CustomerService" > address="jms://" serviceName="customer:CustomerServiceService" > endpointName="customer:CustomerServiceEndpoint" > implementor="com.example.customerservice.impl.CustomerServiceImpl"> > > p:jmsConfig-ref="jmsConfig" /> > > > > The JMSConfiguration bean needs at least a reference to a conncection > factory and a target destination. > > p:connectionFactory-ref="jmsConnectionFactory" > p:targetDestination="test.cxf.jmstransport.queue" > /> > > If your ConnectionFactory does not cache connections you should wrap it in > a spring SingleConnectionFactory. This is necessary because the JMS > Transport creates a new connection for each message and the > SingleConnectionFactory is needed to cache this connection. > > class="org.springframework.jms.connection.SingleConnectionFactory"> > > > > > > > JMSConfiguration options: > Name Default > Description > connectionFactory (mandatory field) Reference to a bean that defines a > jms ConnectionFactory. Remember to wrap the connectionFactory like described > above when not using a pooling ConnectionFactory > wrapInSingleConnectionFactory true Will wrap the connectionFactory with > a Spring SingleConnectionFactory, which can improve the performance of the > jms transport reconnectOnException false If wrapping the > connectionFactory with a Spring SingleConnectionFactory and > reconnectOnException is true, will create a new connection if there is an > exception thrown, otherwise will not try to reconnect if the there is an > exception thrown. targetDestination > JNDI name or provider specific name of a destination. Example for ActiveMQ: > > test.cxf.jmstransport.queue replyDestination > > destinationResolver DynamicDestinationResolver Reference to a Spring > DestinationResolver. This allows to define how destination names are > resolved to jms Destinations. By default a DynamicDestinationResolver is > used. It resolves destinations using the jms providers features. If you > reference a JndiDestinationResolver you can resolve the destination names > using JNDI. > transactionManager > none Reference to a spring transaction manager. This allows to take part > in JTA Transactions with your webservice. > taskExecutor SimpleAsyncTaskExecutor Reference to a spring TaskExecutor. > This is used in listeners to decide how to handle incoming messages. Default > is a spring SimpleAsyncTaskExecutor. > useJms11> CXF 2.1.3: false true means JMS 1.1 features are used > false means only JMS 1.0.2 features are used > messageIdEnabled true messageTimestampEnabled true > cacheLevel -1 Specify the level of caching that the JMS listener > container is allowed to > apply. > Please check out the java doc of the > org.springframework.jms.listenerDefaultMessageListenerContainer for more > information > pubSubNoLocal false true do not receive your own messages when using > topics > receiveTimeout 0 How many milliseconds to wait for response messages. 0 > means wait indefinitely > explicitQosEnabled false true means that QoS parameters are set for each > message. deliveryMode 1 NON_PERSISTENT = 1 messages will only be kept in > memory > > PERSISTENT = 2 messages will be persisted to disk > priority 4 > Priority for the messages. See your JMS provider doc for details > timeToLive 0 After this time the message will be discarded by the jms > provider > sessionTransacted false true means JMS transactions are used > concurrentConsumers 1 minimum number of concurrent consumers for > listener > maxConcurrentConsumers 1 maximum number of concurrent consumers for > listener maxConcurrentTasks 10 Maximum number of threads that handle the > received requests (available from cxf 2.1.4 upwards) messageSelector > > jms selector to filter incoming messages (allows to share a queue) > subscriptionDurable > false durableSubscriptionName > > messageType > text > text > binary > byte > pubSubDomain > false > false means use queues > true means use topics > jmsProviderTibcoEms false true means that the jms provider is Tibco EMS. > Currently this activates that the principal in the SecurityContext is > populated from the header JMS_TIBCO_SENDER. (available from cxf version > 2.2.6) useMessageIDAsCorrealationID false Specifies whether the JMS > broker will use the message ID to correlate messages. By default a CXF > client will set a generated correlation id instead > > > Change Notification > Preferences > View Online| > View > Changes| > Add > Comment > -- ---- http://www.liquid-reality.de