cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r922360 - in /websites/production/cxf/content: cache/docs.pageCache docs/using-the-jmsconfigfeature.html
Date Tue, 16 Sep 2014 07:47:16 GMT
Author: buildbot
Date: Tue Sep 16 07:47:16 2014
New Revision: 922360

Log:
Production update by buildbot for cxf

Modified:
    websites/production/cxf/content/cache/docs.pageCache
    websites/production/cxf/content/docs/using-the-jmsconfigfeature.html

Modified: websites/production/cxf/content/cache/docs.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/cxf/content/docs/using-the-jmsconfigfeature.html
==============================================================================
--- websites/production/cxf/content/docs/using-the-jmsconfigfeature.html (original)
+++ websites/production/cxf/content/docs/using-the-jmsconfigfeature.html Tue Sep 16 07:47:16
2014
@@ -116,14 +116,8 @@ Apache CXF -- Using the JMSConfigFeature
          <td height="100%">
            <!-- Content -->
            <div class="wiki-content">
-<div id="ConfluenceContent"><p>Standard JMS transport configuration in CXF is
done by defining a JMSConduit or JMSDestination. There is however an easier configuration
option more conformant to Spring dependency injection. Additionally the new configuration
offers many 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 configuration.</p>
-
-<p>The following example configs use the <a shape="rect" class="external-link" href="http://static.springframework.org/spring/docs/2.5.x/reference/beans.html"
rel="nofollow">p-namespace</a> from spring 2.5 but the old spring bean style is also
possible.</p>
-
-<p>Inside a features element the JMSConfigFeature can be defined.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;jaxws:client id=&quot;CustomerService&quot;
+<div id="ConfluenceContent"><p>Standard JMS transport configuration in CXF is
done by defining a JMSConduit or JMSDestination. There is however an easier configuration
option more conformant to Spring dependency injection. Additionally the new configuration
offers many 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 configuration.</p><p>The
following example configs use the <a shape="rect" class="external-link" href="http://static.springframework.org/spring/docs/2.5.x/reference/beans.html"
rel="nofollow">p-namespace</a> from spring 2.5 but the old spring bean style is also
possible.</p><p>Inside a features element the JMSConfigFeature can be defined.</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[&lt;jaxws:client
id=&quot;CustomerService&quot;
 	xmlns:customer=&quot;http://customerservice.example.com/&quot;
 	serviceName=&quot;customer:CustomerServiceService&quot;
 	endpointName=&quot;customer:CustomerServiceEndpoint&quot; address=&quot;jms://&quot;
@@ -135,13 +129,8 @@ Apache CXF -- Using the JMSConfigFeature
 	&lt;/jaxws:features&gt;
 &lt;/jaxws:client&gt;
 ]]></script>
-</div></div>
-<p>In the above example it references a bean "jmsConfig" where the whole configuration
for the JMS transport can be done.</p>
-
-<p>A jaxws Endpoint can be defined in the same way:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;jaxws:endpoint
+</div></div><p>In the above example it references a bean "jmsConfig" where
the whole configuration for the JMS transport can be done.</p><p>A jaxws Endpoint
can be defined in the same way:</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[&lt;jaxws:endpoint
 	xmlns:customer=&quot;http://customerservice.example.com/&quot;
 	id=&quot;CustomerService&quot;
 	address=&quot;jms://&quot;
@@ -154,22 +143,14 @@ Apache CXF -- Using the JMSConfigFeature
 	&lt;/jaxws:features&gt;
 &lt;/jaxws:endpoint&gt;
 ]]></script>
-</div></div>
-
-
-<p>The JMSConfiguration bean needs at least a reference to a conncection factory and
a target destination.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;bean id=&quot;jmsConfig&quot; class=&quot;org.apache.cxf.transport.jms.JMSConfiguration&quot;
+</div></div><p>The JMSConfiguration bean needs at least a reference to
a conncection factory and a target destination.</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[&lt;bean
id=&quot;jmsConfig&quot; class=&quot;org.apache.cxf.transport.jms.JMSConfiguration&quot;
 	p:connectionFactory-ref=&quot;jmsConnectionFactory&quot;
 	p:targetDestination=&quot;test.cxf.jmstransport.queue&quot;
 /&gt;
 ]]></script>
-</div></div>
-<p>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.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;bean id=&quot;jmsConnectionFactory&quot; class=&quot;org.springframework.jms.connection.SingleConnectionFactory&quot;&gt;
+</div></div><p>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.</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[&lt;bean
id=&quot;jmsConnectionFactory&quot; class=&quot;org.springframework.jms.connection.SingleConnectionFactory&quot;&gt;
 	&lt;property name=&quot;targetConnectionFactory&quot;&gt;
 		&lt;bean class=&quot;org.apache.activemq.ActiveMQConnectionFactory&quot;&gt;
 			&lt;property name=&quot;brokerURL&quot; value=&quot;tcp://localhost:61616&quot;
/&gt;
@@ -177,15 +158,8 @@ Apache CXF -- Using the JMSConfigFeature
 	&lt;/property&gt;
 &lt;/bean&gt;
 ]]></script>
-</div></div>
-
-<h2 id="UsingtheJMSConfigFeature-UsingJMSConfigurationfromJava">Using JMSConfiguration
from Java</h2>
-
-<p>To do this from Java, you need to initialize a JMSConfiguration object, then store
a reference to it in a JMSConfigFeature, and then add that to the features in the server factory.
The code that follows is fragmentary. Note that you can't use query parameters in the endpoint
URI that you set in the server factory, all the configuration has to be in the JMSConfiguration
object.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-public static JMSConfiguration newJMSConfiguration(String taskId, String jmsBrokerUrl) {
+</div></div><h2 id="UsingtheJMSConfigFeature-UsingJMSConfigurationfromJava">Using
JMSConfiguration from Java</h2><p>To do this from Java, you need to initialize
a JMSConfiguration object, then store a reference to it in a JMSConfigFeature, and then add
that to the features in the server factory. The code that follows is fragmentary. Note that
you can't use query parameters in the endpoint URI that you set in the server factory, all
the configuration has to be in the JMSConfiguration object.</p><div class="code panel
pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[public
static JMSConfiguration newJMSConfiguration(String taskId, String jmsBrokerUrl) {
         String destinationUri = &quot;jms:queue:&quot; + taskId;
         JMSConfiguration conf = new JMSConfiguration();
         conf.setRequestURI(destinationUri);
@@ -215,21 +189,7 @@ public static JMSConfiguration newJMSCon
         server = svrFactory.create();
 }
 ]]></script>
-</div></div>
-
-
-<h2 id="UsingtheJMSConfigFeature-JMSConfigurationoptions">JMSConfiguration options</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th
colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th
colspan="1" rowspan="1" class="confluenceTh"><p> Description <br clear="none"
class="atl-forced-newline"> </p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> connectionFactory </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> 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 <br clear="none" class="atl-forced-newline">
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
wrapInSingleConnectionFactory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
Will wrap the connectionFactory with a Spring SingleConnectionFactory, which can improve the
performance of the jms transport.  Default is true. </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> r
 econnectOnException </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
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. Default is false. </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> targetDestination </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> JNDI name or provider specific name
of a destination. Example for ActiveMQ: <br clear="none" class="atl-forced-newline">
-test.cxf.jmstransport.queue </p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> replyDestination </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <br clear="none" class="atl-forced-newline">
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
destinationResolver </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
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. <br clear="none" class="atl-forced-newline">
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
transactionManager <br clear="none" class="atl-forced-newline"> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> Reference to a spring transaction
manager. This allows to
  take part in JTA Transactions with your webservice. <br clear="none" class="atl-forced-newline">
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
taskExecutor </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
Reference to a spring TaskExecutor. This is used in listeners to decide how to handle incoming
messages. Default is a spring SimpleAsyncTaskExecutor. <br clear="none" class="atl-forced-newline">
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
useJms11 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
true means JMS 1.1 features are used <br clear="none" class="atl-forced-newline">
-false means only JMS 1.0.2 features are used.  Default is false. <br clear="none" class="atl-forced-newline">
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
messageIdEnabled </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
Default is true. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> messageTimestampEnabled </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> Default is true. </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> cacheLevel </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> Specify the level of caching that
the JMS listener container is allowed to apply. <br clear="none" class="atl-forced-newline">
-Please check out the java doc of the org.springframework.jms.listenerDefaultMessageListenerContainer
for more information.  Default is -1. <br clear="none" class="atl-forced-newline"> </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> pubSubNoLocal </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> If true, do not receive your own
messages when using topics.  Default is false. <br clear="none" class="atl-forced-newline">
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
receiveTimeout </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
How many milliseconds to wait for response messages. 0 (default) means wait indefinitely.
<br clear="none" class="atl-forced-newline"> </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> explicitQosEnabled </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> If true, means that QoS parameters
are set for each message.  Default is false. </p></td></tr><tr><td
cols
 pan="1" rowspan="1" class="confluenceTd"><p> deliveryMode </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> NON_PERSISTENT = 1 (default) messages
will be kept only in memory <br clear="none" class="atl-forced-newline">
-<br clear="none" class="atl-forced-newline">
-PERSISTENT = 2&#160;&#160;&#160; messages will be persisted to disk <br clear="none"
class="atl-forced-newline"> </p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> priority </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> Priority for the messages. Default is 4. See
your JMS provider doc for details <br clear="none" class="atl-forced-newline"> </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> timeToLive </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> After this time the message will
be discarded by the jms provider (default 0). <br clear="none" class="atl-forced-newline">
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
sessionTransacted </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
If true, means JMS transactions are used. (Default is false). <br clear="none" class="atl-forced-newline">
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
concurrentConsumers <
 /p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Minimum
number of concurrent consumers for listener (default 1). <br clear="none" class="atl-forced-newline">
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
maxConcurrentConsumers </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
Maximum number of concurrent consumers for listener (default 1). </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> maxConcurrentTasks </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> (<strong>deprecated</strong>)
Maximum number of threads that handle the received requests (Default 10). </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> messageSelector <br clear="none"
class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
jms selector to filter incoming messages (allows to share a queue) <br clear="none" class="atl-forced-newline">
</p></td></tr><tr><td colspan="1" rowspan="
 1" class="confluenceTd"><p> subscriptionDurable <br clear="none" class="atl-forced-newline">
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Default
false. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
durableSubscriptionName <br clear="none" class="atl-forced-newline"> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>&#160;</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> messageType <br clear="none"
class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
text (default) <br clear="none" class="atl-forced-newline">
-binary <br clear="none" class="atl-forced-newline">
-byte <br clear="none" class="atl-forced-newline"> </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> pubSubDomain <br clear="none"
class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
false (default) means use queues <br clear="none" class="atl-forced-newline">
-true means use topics <br clear="none" class="atl-forced-newline"> </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> jmsProviderTibcoEms </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> true means that the jms provider
is Tibco EMS. Default is false.  Currently this activates that the principal in the SecurityContext
is populated from the header JMS_TIBCO_SENDER. (available from cxf version 2.2.6) </p></td></tr></tbody></table></div>
-
-<p><br clear="none" class="atl-forced-newline"></p></div>
+</div></div><h2 id="UsingtheJMSConfigFeature-JMSConfigurationoptions">JMSConfiguration
options</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th
colspan="1" rowspan="1" class="confluenceTh"><p>Name</p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>connectionFactory</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>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</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>wrapInSingleConnectionFactory</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><span>This option was removed
since CXF 3.0.0. </span>Will wrap the connectionFactory with a Spring SingleConnectionFactory,
which can improve the performance of the jms transport. Default is true.</p></td></tr><tr><td

 colspan="1" rowspan="1" class="confluenceTd"><p>reconnectOnException</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><span>(</span><strong>deprecated</strong><span>)
</span>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. Default is false. From CXF 3.0.0, CXF
always <span style="line-height: 1.4285715;">reconnect on exceptions</span></p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>targetDestination</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>JNDI name or provider specific name
of a destination. Example for ActiveMQ: <br clear="none" class="atl-forced-newline">
test.cxf.jmstransport.queue</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>destinationResolver</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>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.</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>transactionManager</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Reference to a spring transaction
manager. This allows to take part in JTA Transactions with your webservice.</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>taskExecutor</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><span>This option was removed
since CXF 3.0.0. </span>Reference to a spring TaskExecutor. This is used in listeners
to decide how to handle incoming messages. Default is a spring SimpleAsyncTaskExecutor.</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>useJms11</p></
 td><td colspan="1" rowspan="1" class="confluenceTd"><p>This option was removed
since CXF 3.0.0.</p><p>true means JMS 1.1 features are used <br clear="none"
class="atl-forced-newline"> false means only JMS 1.0.2 features are used. Default is false.</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>messageIdEnabled</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Default is true. <span>This
option was removed since CXF 3.0.0.</span></p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>messageTimestampEnabled</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Default is true. <span>This
option was removed since CXF 3.0.0.</span></p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>cacheLevel</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><span>This option was removed
since CXF 3.0.0.</span></p><p>Specify the level of caching that the JMS
listener container is allowed to apply. <br clear="none" class="at
 l-forced-newline"> Please check out the java doc of the org.springframework.jms.listenerDefaultMessageListenerContainer
for more information. Default is -1.</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>pubSubNoLocal</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>If true, do not receive your own messages when
using topics. Default is false.</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>receiveTimeout</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>How many milliseconds to wait for response messages.
0 (default) means wait indefinitely. since CXF 3.0, the default value is changed to 60000
(60 seconds)</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>explicitQosEnabled</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>If true, means that QoS parameters
are set for each message. Default is false.</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>deliveryMode</p></td><
 td colspan="1" rowspan="1" class="confluenceTd"><p>NON_PERSISTENT = 1 messages will
be kept only in memory <br clear="none" class="atl-forced-newline"> <br clear="none"
class="atl-forced-newline"> PERSISTENT = 2&#160;<span>(default)</span>&#160;&#160;messages
will be persisted to disk</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>priority</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Priority for the messages. Default is 4. See your JMS provider
doc for details</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>timeToLive</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>After this time the message will
be discarded by the jms provider (default 0).</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>sessionTransacted</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>If true, means JMS transactions are
used. (Default is false).</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd">
 <p>concurrentConsumers</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><span>This
option was removed since CXF 3.0.0. </span>Minimum number of concurrent consumers for
listener (default 1).</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>maxConcurrentConsumers</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><span>This option was removed since CXF
3.0.0. </span>Maximum number of concurrent consumers for listener (default 1).</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>maxConcurrentTasks</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><span>This option was removed
since CXF 3.0.0. </span>(<strong>deprecated</strong>) Maximum number of
threads that handle the received requests (Default 10).</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>messageSelector</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>jms selector to filter incoming messages
(allows to share a queue)</p></t
 d></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>subscriptionDurable</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Default false.</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>durableSubscriptionName</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>&#160;</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>messageType</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>text (default) <br clear="none"
class="atl-forced-newline"> binary <br clear="none" class="atl-forced-newline"> byte</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>pubSubDomain</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>false (default) means use queues
<br clear="none" class="atl-forced-newline"> true means use topics</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>jmsProviderTibcoEms</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>true means that the jms provid
 er is Tibco EMS. Default is false. Currently this activates that the principal in the SecurityContext
is populated from the header JMS_TIBCO_SENDER. (available from cxf version 2.2.6)</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p class="p1">maxSuspendedContinuations</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><strong>Since CXF 3.0.0</strong>,
The max suspended continuations that the JMS destination could have, if the current suspended
continuations number exceeds the max value, the <span style="line-height: 1.4285715;">JMSListenerContainer
will be stopped. </span>The default value is -1, which means disable this feature.</td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p class="p1">reconnectPercentOfMax</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><strong>Since CXF 3.0.0, </strong>If
the <span>JMSListenerContainer is stopped due to the current suspended continuation
exceeds the max value, the JMSListenerContainer will be 
 restarted when the current suspended continuation below the value of (<span>maxSuspendedContinuations*<span>reconnectPercentOfMax/100).</span></span></span>
The default value is 70.</td></tr></tbody></table></div></div>
            </div>
            <!-- Content -->
          </td>



Mime
View raw message