Author: buildbot
Date: Wed Oct  9 16:47:54 2013
New Revision: 881911

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 Wed 
Oct  9 16:47:54 2013
@@ -241,7 +241,7 @@ Please check out the java doc of the org
 PERSISTENT = 2&#160;&#160;&#160; messages will be persisted to disk <br 
clear="none" class="atl-forced-newline"> </td></tr><tr><td colspan="1" 
rowspan="1" class="confluenceTd"> priority </td><td colspan="1" rowspan="1" 
class="confluenceTd"> Priority for the messages. Default is 4. See your JMS 
provider doc for details <br clear="none" class="atl-forced-newline"> 
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> timeToLive 
</td><td colspan="1" rowspan="1" class="confluenceTd"> After this time the 
message will be discarded by the jms provider (default 0). <br clear="none" 
class="atl-forced-newline"> </td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"> sessionTransacted </td><td colspan="1" rowspan="1" 
class="confluenceTd"> If true, means JMS transactions are used. (Default is 
false). <br clear="none" class="atl-forced-newline"> </td></tr><tr><td 
colspan="1" rowspan="1" class="confluenceTd"> concurrentConsumers </td><td 
colspan="1" rowspan="1" class="confluence
 Td"> Minimum number of concurrent consumers for listener (default 1). <br 
clear="none" class="atl-forced-newline"> </td></tr><tr><td colspan="1" 
rowspan="1" class="confluenceTd"> maxConcurrentConsumers </td><td colspan="1" 
rowspan="1" class="confluenceTd"> Maximum number of concurrent consumers for 
listener (default 1). </td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"> maxConcurrentTasks </td><td colspan="1" rowspan="1" 
class="confluenceTd"> (<b>deprecated</b>) Maximum number of threads that handle 
the received requests (Default 10). </td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"> messageSelector <br clear="none" 
class="atl-forced-newline"> </td><td colspan="1" rowspan="1" 
class="confluenceTd"> jms selector to filter incoming messages (allows to share 
a queue) <br clear="none" class="atl-forced-newline"> </td></tr><tr><td 
colspan="1" rowspan="1" class="confluenceTd"> subscriptionDurable <br 
clear="none" class="atl-forced-newline"> </td><td colspan="1" r
 owspan="1" class="confluenceTd"> Default false. </td></tr><tr><td colspan="1" 
rowspan="1" class="confluenceTd"> durableSubscriptionName <br clear="none" 
class="atl-forced-newline"> </td><td colspan="1" rowspan="1" 
class="confluenceTd">&#160;</td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"> messageType <br clear="none" class="atl-forced-newline"> 
</td><td colspan="1" rowspan="1" class="confluenceTd"> 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"> </td></tr><tr><td 
colspan="1" rowspan="1" class="confluenceTd"> pubSubDomain <br clear="none" 
class="atl-forced-newline"> </td><td colspan="1" rowspan="1" 
class="confluenceTd"> false (default) means use queues <br clear="none" 
class="atl-forced-newline">
-true means use topics <br clear="none" class="atl-forced-newline"> 
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> 
jmsProviderTibcoEms </td><td colspan="1" rowspan="1" class="confluenceTd"> 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) </td></tr><tr><td 
colspan="1" rowspan="1" class="confluenceTd"> useMessageIDAsCorrelationID 
</td><td colspan="1" rowspan="1" class="confluenceTd"> If true, specifies JMS 
broker will use the message ID to correlate messages. By default (false) a CXF 
client will set a generated correlation id instead </td></tr></tbody></table>
+true means use topics <br clear="none" class="atl-forced-newline"> 
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> 
jmsProviderTibcoEms </td><td colspan="1" rowspan="1" class="confluenceTd"> 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) 
</td></tr></tbody></table>
 </div>
 
 <p><br clear="none" class="atl-forced-newline"></p></div>


Reply via email to