cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r906502 [5/7] - in /websites/production/cxf/content: cache/ docs/
Date Tue, 22 Apr 2014 12:47:36 GMT
Added: websites/production/cxf/content/docs/jms-performance-and-pooling.html
==============================================================================
--- websites/production/cxf/content/docs/jms-performance-and-pooling.html (added)
+++ websites/production/cxf/content/docs/jms-performance-and-pooling.html Tue Apr 22 12:47:36 2014
@@ -0,0 +1,177 @@
+
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+<html>
+  <head>
+
+<link type="text/css" rel="stylesheet" href="/resources/site.css">
+<script src='/resources/space.js'></script>
+
+<meta http-equiv="Content-type" content="text/html;charset=UTF-8">
+<meta name="keywords" content="business integration, EAI, SOA, Service Oriented Architecture, web services, SOAP, JBI, JMS, WSDL, XML, EDI, Electronic Data Interchange, standards support, integration standards, application integration, middleware, software, solutions, services, CXF, open source">
+<meta name="description" content="Apache CXF, Services Framework - JMS performance and pooling">
+
+
+<link type="text/css" rel="stylesheet" href="/resources/highlighter/styles/shCoreCXF.css">
+<link type="text/css" rel="stylesheet" href="/resources/highlighter/styles/shThemeCXF.css">
+
+<script src='/resources/highlighter/scripts/shCore.js'></script>
+<script src='/resources/highlighter/scripts/shBrushJava.js'></script>
+<script>
+  SyntaxHighlighter.defaults['toolbar'] = false;
+  SyntaxHighlighter.all();
+</script>
+
+
+    <title>
+Apache CXF -- JMS performance and pooling
+    </title>
+  </head>
+<body onload="init()">
+
+
+<table width="100%" cellpadding="0" cellspacing="0">
+  <tr>
+    <td id="cell-0-0" colspan="2">&nbsp;</td>
+    <td id="cell-0-1">&nbsp;</td>
+    <td id="cell-0-2" colspan="2">&nbsp;</td>
+  </tr>
+  <tr>
+    <td id="cell-1-0">&nbsp;</td>
+    <td id="cell-1-1">&nbsp;</td>
+    <td id="cell-1-2">
+      <!-- Banner -->
+<div class="banner" id="banner"><div><table border="0" cellpadding="0" cellspacing="0" width="100%"><tr><td align="left" colspan="1" nowrap>
+<a shape="rect" href="http://cxf.apache.org/" title="Apache CXF"><span style="font-weight: bold; font-size: 170%; color: white">Apache CXF</span></a>
+</td><td align="right" colspan="1" nowrap>
+<a shape="rect" href="http://www.apache.org/" title="The Apache Sofware Foundation"><img border="0" alt="ASF Logo" src="http://cxf.apache.org/images/asf-logo.png"></a>
+</td></tr></table></div></div>
+      <!-- Banner -->
+      <div id="top-menu">
+        <table border="0" cellpadding="1" cellspacing="0" width="100%">
+          <tr>
+            <td>
+              <div align="left">
+                <!-- Breadcrumbs -->
+<a href="index.html">Index</a>&nbsp;&gt;&nbsp;<a href="transports.html">Transports</a>&nbsp;&gt;&nbsp;<a href="jms-transport.html">JMS Transport</a>&nbsp;&gt;&nbsp;<a href="jms-performance-and-pooling.html">JMS performance and pooling</a>
+                <!-- Breadcrumbs -->
+              </div>
+            </td>
+            <td>
+              <div align="right">
+                <!-- Quicklinks -->
+<div id="quicklinks"><p><a shape="rect" href="http://cxf.apache.org/download.html">Download</a> | <a shape="rect" href="http://cxf.apache.org/docs/index.html">Documentation</a></p></div>
+                <!-- Quicklinks -->
+              </div>
+            </td>
+          </tr>
+        </table>
+      </div>
+    </td>
+    <td id="cell-1-3">&nbsp;</td>
+    <td id="cell-1-4">&nbsp;</td>
+  </tr>
+  <tr>
+    <td id="cell-2-0" colspan="2">&nbsp;</td>
+    <td id="cell-2-1">
+      <table>
+        <tr valign="top">
+          <td height="100%">
+            <div id="wrapper-menu-page-right">
+              <div id="wrapper-menu-page-top">
+                <div id="wrapper-menu-page-bottom">
+                  <div id="menu-page">
+                    <!-- NavigationBar -->
+<div id="navigation"><ul class="alternate"><li><a shape="rect" href="overview.html">Overview</a></li><li><a shape="rect" href="how-tos.html">How-Tos</a></li><li><a shape="rect" href="frontends.html">Frontends</a></li><li><a shape="rect" href="databindings.html">DataBindings</a></li><li><a shape="rect" href="transports.html">Transports</a></li><li><a shape="rect" href="configuration.html">Configuration</a></li><li><a shape="rect" href="debugging-and-logging.html">Debugging and Logging</a></li><li><a shape="rect" href="tools.html">Tools</a></li><li><a shape="rect" href="restful-services.html">RESTful Services</a></li><li><a shape="rect" href="wsdl-bindings.html">WSDL Bindings</a></li><li><a shape="rect" href="service-routing.html">Service Routing</a></li><li><a shape="rect" href="dynamic-languages.html">Dynamic Languages</a></li><li><a shape="rect" href="ws-support.html">WS-* Support</a></li><li><a shape="rect" href="advanced-integration.html">Advanced Integration</a></li><li><a shape
 ="rect" href="deployment.html">Deployment</a></li><li><a shape="rect" href="schemas-and-namespaces.html">Use of Schemas and Namespaces</a></li></ul><hr><ul class="alternate"><li><p>Search</p></li></ul><form enctype="application/x-www-form-urlencoded" method="get" id="cse-search-box" action="http://www.google.com/cse">
+  <div>
+    <input type="hidden" name="cx" value="002890367768291051730:o99qiwa09y4">
+    <input type="hidden" name="ie" value="UTF-8">
+    <input type="text" name="q" size="21">
+    <input type="submit" name="sa" value="Search">
+  </div>
+</form>
+<script type="text/javascript" src="http://www.google.com/cse/brand?form=cse-search-box&amp;lang=en"></script><hr><ul class="alternate"><li><a shape="rect" href="http://cxf.apache.org/javadoc/latest/">API 2.x (Javadoc)</a></li><li><a shape="rect" href="http://cxf.apache.org/javadoc/latest-3.0.x/">API 3.x (Javadoc)</a></li><li><a shape="rect" href="http://cxf.apache.org/">CXF Website</a></li></ul></div>
+                    <!-- NavigationBar -->
+                  </div>
+              </div>
+            </div>
+          </div>
+         </td>
+         <td height="100%">
+           <!-- Content -->
+           <div class="wiki-content">
+<div id="ConfluenceContent"><p>CXF JMS should be very fast if configured correctly. There are two major settings that affect performance: pooling and synchronous receives on client side.</p><h2 id="JMSperformanceandpooling-Pooling">Pooling</h2><p>On the client side CXF creates a new JMS Session and Producer for each message. This is necessary as these JMS objects are not thread safe. Especially creating a Producer is very time intensive though as a communication with the server is necessary.</p><p>Connection Factory pools help to improve perfomance by caching the Connection, Session and Producer.</p><p>For ActiveMQ configuring pooling is quite simple:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Pooling for ActiveMQ</b></div><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[import org.apache.activemq.ActiveMQConnectionFactory;
+import org.apache.activemq.pool.PooledConnectionFactory;
+
+ConnectionFactory cf = new ActiveMQConnectionFactory(&quot;tcp://localhost:61616&quot;);
+PooledConnectionFactory pcf = new PooledConnectionFactory();
+pcf.setExpiryTimeout(5000); // Make sure to set expiry timeout as the default of 0 prevents reconnect on failures
+pcf.setConnectionFactory(cf);
+
+JMSConfiguration jmsConfig = new JMSConfiguration();
+jmsConfig.setConnectionFactory(pcf);]]></script>
+</div></div><h2 id="JMSperformanceandpooling-SynchronousReceivesonclientside">Synchronous Receives on client side</h2><p>For request / reply exchanges the JMS transport sends a request and waits for a reply. Whenever possible this is done using a JMS MessageListener. In some cases though CXF has to use a synchronous Consumer.receive() instead. The problem here is that CXF needs to be able to share queues between endpoints. So a MessageListener needs to use a MessageSelector to filter the messages. This selector needs to be known in advance so the listener can be opened once.</p><p>There are two cases where this is not possible:</p><ol><li>MessageIdAsCorrelationId: If useConduitIdSelector is false and no static conduitIdSelectorPrefix is given then the client does not set a correlation id. The server then uses the message id of the request message as correlation id. As this id can not be known in advance the client has to use a synchronous Consumer.receive. This pattern is also neces
 sary for communication with IBM JMS endpoints as they use this by default</li><li>The user can set the JMSMessageHeadersType in the request message and there do a SetJMSCorrelationID("customid"). In this case CXF also has to use a synchronous Consumer.receive()</li></ol><p>So the general rule here is to avoid these settings that lead to the synchronous receives.</p><h2 id="JMSperformanceandpooling-Expectedperfomance">Expected perfomance</h2><p>On a fast system (Intel Core i7) and with small messages CXF can achieve a performance of about 12,000 messages per second for one way and 3,500 transactions / second for request reply (both non persistent). If you measure much lower speeds then you might have an issue with your JMS configuration.</p><p>&#160;</p></div>
+           </div>
+           <!-- Content -->
+         </td>
+        </tr>
+      </table>
+   </td>
+   <td id="cell-2-2" colspan="2">&nbsp;</td>
+  </tr>
+  <tr>
+   <td id="cell-3-0">&nbsp;</td>
+   <td id="cell-3-1">&nbsp;</td>
+   <td id="cell-3-2">
+     <div id="footer">
+       <!-- Footer -->
+       <div id="site-footer">
+         <a href="http://cxf.apache.org/privacy-policy.html">Privacy Policy</a> - 
+         (<a href="https://cwiki.apache.org/confluence/pages/editpage.action?pageId=40508998">edit page</a>) 
+	 (<a href="https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=40508998&amp;showComments=true&amp;showCommentArea=true#addcomment">add comment</a>)<br>
+	Apache CXF, CXF, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.<br>
+        All other marks mentioned may be trademarks or registered trademarks of their respective owners.
+       </div>
+       <!-- Footer -->
+     </div>
+   </td>
+   <td id="cell-3-3">&nbsp;</td>
+   <td id="cell-3-4">&nbsp;</td>
+  </tr>
+  <tr>
+    <td id="cell-4-0" colspan="2">&nbsp;</td>
+    <td id="cell-4-1">&nbsp;</td>
+    <td id="cell-4-2" colspan="2">&nbsp;</td>
+  </tr>
+</table>
+
+<script type="text/javascript">
+var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
+document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
+</script>
+<script type="text/javascript">
+try {
+var pageTracker = _gat._getTracker("UA-4458903-1");
+pageTracker._trackPageview();
+} catch(err) {}</script>
+
+</body>
+</html>
+

Added: websites/production/cxf/content/docs/jms-transactions.html
==============================================================================
--- websites/production/cxf/content/docs/jms-transactions.html (added)
+++ websites/production/cxf/content/docs/jms-transactions.html Tue Apr 22 12:47:36 2014
@@ -0,0 +1,188 @@
+
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+<html>
+  <head>
+
+<link type="text/css" rel="stylesheet" href="/resources/site.css">
+<script src='/resources/space.js'></script>
+
+<meta http-equiv="Content-type" content="text/html;charset=UTF-8">
+<meta name="keywords" content="business integration, EAI, SOA, Service Oriented Architecture, web services, SOAP, JBI, JMS, WSDL, XML, EDI, Electronic Data Interchange, standards support, integration standards, application integration, middleware, software, solutions, services, CXF, open source">
+<meta name="description" content="Apache CXF, Services Framework - JMS transactions">
+
+
+<link type="text/css" rel="stylesheet" href="/resources/highlighter/styles/shCoreCXF.css">
+<link type="text/css" rel="stylesheet" href="/resources/highlighter/styles/shThemeCXF.css">
+
+<script src='/resources/highlighter/scripts/shCore.js'></script>
+<script src='/resources/highlighter/scripts/shBrushJava.js'></script>
+<script src='/resources/highlighter/scripts/shBrushXml.js'></script>
+<script src='/resources/highlighter/scripts/shBrushPlain.js'></script>
+<script>
+  SyntaxHighlighter.defaults['toolbar'] = false;
+  SyntaxHighlighter.all();
+</script>
+
+
+    <title>
+Apache CXF -- JMS transactions
+    </title>
+  </head>
+<body onload="init()">
+
+
+<table width="100%" cellpadding="0" cellspacing="0">
+  <tr>
+    <td id="cell-0-0" colspan="2">&nbsp;</td>
+    <td id="cell-0-1">&nbsp;</td>
+    <td id="cell-0-2" colspan="2">&nbsp;</td>
+  </tr>
+  <tr>
+    <td id="cell-1-0">&nbsp;</td>
+    <td id="cell-1-1">&nbsp;</td>
+    <td id="cell-1-2">
+      <!-- Banner -->
+<div class="banner" id="banner"><div><table border="0" cellpadding="0" cellspacing="0" width="100%"><tr><td align="left" colspan="1" nowrap>
+<a shape="rect" href="http://cxf.apache.org/" title="Apache CXF"><span style="font-weight: bold; font-size: 170%; color: white">Apache CXF</span></a>
+</td><td align="right" colspan="1" nowrap>
+<a shape="rect" href="http://www.apache.org/" title="The Apache Sofware Foundation"><img border="0" alt="ASF Logo" src="http://cxf.apache.org/images/asf-logo.png"></a>
+</td></tr></table></div></div>
+      <!-- Banner -->
+      <div id="top-menu">
+        <table border="0" cellpadding="1" cellspacing="0" width="100%">
+          <tr>
+            <td>
+              <div align="left">
+                <!-- Breadcrumbs -->
+<a href="index.html">Index</a>&nbsp;&gt;&nbsp;<a href="transports.html">Transports</a>&nbsp;&gt;&nbsp;<a href="jms-transport.html">JMS Transport</a>&nbsp;&gt;&nbsp;<a href="jms-transactions.html">JMS transactions</a>
+                <!-- Breadcrumbs -->
+              </div>
+            </td>
+            <td>
+              <div align="right">
+                <!-- Quicklinks -->
+<div id="quicklinks"><p><a shape="rect" href="http://cxf.apache.org/download.html">Download</a> | <a shape="rect" href="http://cxf.apache.org/docs/index.html">Documentation</a></p></div>
+                <!-- Quicklinks -->
+              </div>
+            </td>
+          </tr>
+        </table>
+      </div>
+    </td>
+    <td id="cell-1-3">&nbsp;</td>
+    <td id="cell-1-4">&nbsp;</td>
+  </tr>
+  <tr>
+    <td id="cell-2-0" colspan="2">&nbsp;</td>
+    <td id="cell-2-1">
+      <table>
+        <tr valign="top">
+          <td height="100%">
+            <div id="wrapper-menu-page-right">
+              <div id="wrapper-menu-page-top">
+                <div id="wrapper-menu-page-bottom">
+                  <div id="menu-page">
+                    <!-- NavigationBar -->
+<div id="navigation"><ul class="alternate"><li><a shape="rect" href="overview.html">Overview</a></li><li><a shape="rect" href="how-tos.html">How-Tos</a></li><li><a shape="rect" href="frontends.html">Frontends</a></li><li><a shape="rect" href="databindings.html">DataBindings</a></li><li><a shape="rect" href="transports.html">Transports</a></li><li><a shape="rect" href="configuration.html">Configuration</a></li><li><a shape="rect" href="debugging-and-logging.html">Debugging and Logging</a></li><li><a shape="rect" href="tools.html">Tools</a></li><li><a shape="rect" href="restful-services.html">RESTful Services</a></li><li><a shape="rect" href="wsdl-bindings.html">WSDL Bindings</a></li><li><a shape="rect" href="service-routing.html">Service Routing</a></li><li><a shape="rect" href="dynamic-languages.html">Dynamic Languages</a></li><li><a shape="rect" href="ws-support.html">WS-* Support</a></li><li><a shape="rect" href="advanced-integration.html">Advanced Integration</a></li><li><a shape
 ="rect" href="deployment.html">Deployment</a></li><li><a shape="rect" href="schemas-and-namespaces.html">Use of Schemas and Namespaces</a></li></ul><hr><ul class="alternate"><li><p>Search</p></li></ul><form enctype="application/x-www-form-urlencoded" method="get" id="cse-search-box" action="http://www.google.com/cse">
+  <div>
+    <input type="hidden" name="cx" value="002890367768291051730:o99qiwa09y4">
+    <input type="hidden" name="ie" value="UTF-8">
+    <input type="text" name="q" size="21">
+    <input type="submit" name="sa" value="Search">
+  </div>
+</form>
+<script type="text/javascript" src="http://www.google.com/cse/brand?form=cse-search-box&amp;lang=en"></script><hr><ul class="alternate"><li><a shape="rect" href="http://cxf.apache.org/javadoc/latest/">API 2.x (Javadoc)</a></li><li><a shape="rect" href="http://cxf.apache.org/javadoc/latest-3.0.x/">API 3.x (Javadoc)</a></li><li><a shape="rect" href="http://cxf.apache.org/">CXF Website</a></li></ul></div>
+                    <!-- NavigationBar -->
+                  </div>
+              </div>
+            </div>
+          </div>
+         </td>
+         <td height="100%">
+           <!-- Content -->
+           <div class="wiki-content">
+<div id="ConfluenceContent"><p>CXF supports resource local jms transactions and JTA transactions on CXF endpoints when using one way messages.</p><h2 id="JMStransactions-ResourcelocalJMStransactions">Resource local JMS transactions</h2><p>This kind of transaction is easy to configure but will only roll back the JMS message. It will not directly coordinate other resources like a database transaction.</p><p>Simply configure the endpoint normally and set the propety "sessionTransacted" to true. CXF will then roll back the message on if any exception happens.</p><h2 id="JMStransactions-JTAtransactions">JTA transactions</h2><p>JTA transactions allow to coordinate any number of XA resources. If a CXF endpoint is configured for JTA transactions it will start a JTA transaction before calling the service impl. If no exceptions happen the transaction will be committed in case of any exception the transaction will be rolled back. This allows to e.g. transactionally consume a JMS message and wr
 ite the data into a database. In case of an exception both resources will be rolled back. So either the message is consumed AND the database record is written or the message is rolled back AND the database record is not written.</p><h3 id="JMStransactions-ThefirstconfigneededforJTAisatransactionmanager:">The first config needed for JTA is a transaction manager:</h3><p>Either create a transaction manager in a bean using:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Define transaction manager</b></div><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[&lt;bean id =&quot;transactionManager&quot; class=&quot;org.apache.geronimo.transaction.manager.GeronimoTransactionManager&quot;/&gt;]]></script>
+</div></div><p>as an OSGi service reference. (This search filter can vary between application servers).</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Lookup transaction manager as OSGi service using blueprint</b></div><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[&lt;reference id=&quot;TransactionManager&quot; interface=&quot;javax.transaction.TransactionManager&quot;/&gt;]]></script>
+</div></div><p>Then the name of the TransactionManager can be set in the JMS URI</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>JMS URI with transaction manager</b></div><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: text; gutter: false" type="syntaxhighlighter"><![CDATA[jms:queue:myqueue?jndiTransactionManager=TransactionManager
+jms:jndi:myqueue?jndiTransactionManager=java:comp/env/TransactionManager]]></script>
+</div></div><p>The first would find a bean with id "TransactionManager" the second would look up the transaction manager in JNDI.</p><h3 id="JMStransactions-ThesecondconfigisaJCApoolingconnectionfactory">The second config is a JCA pooling connection factory</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>JCA pooling connection factory defined using spring</b></div><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[&lt;bean id=&quot;xacf&quot; class=&quot;org.apache.activemq.ActiveMQXAConnectionFactory&quot;&gt;
+  &lt;property name=&quot;brokerURL&quot; value=&quot;tcp://localhost:61616&quot;/&gt;
+&lt;/bean&gt;
+&lt;bean id=&quot;ConnectionFactory&quot; class=&quot;org.apache.activemq.jms.pool.JcaPooledConnectionFactory&quot;&gt;
+  &lt;property name=&quot;transactionManager&quot; ref=&quot;transactionManager&quot;/&gt;
+  &lt;property name=&quot;connectionFactory&quot; ref=&quot;xacf&quot;/&gt;
+&lt;/bean&gt;]]></script>
+</div></div><p>This first defines an ActiveMQ XA connection factory. This is then given to a JcaPoolingConnectionFactory which is then provided as the default bean with id "ConnectionFactory".</p>    <div class="aui-message hint shadowed information-macro">
+                            <span class="aui-icon icon-hint">Icon</span>
+                <div class="message-content">
+                            It is important here that JcaPoolingConnectionFactory looks like a normal ConnectionFactory. When a new connection and session are opened it checks for an XA tranaction and automatically registers the JMS session as an XA resource. This allows the JMS session to participate in the JMS transaction. Do not directly set an XAConnectionFactory for the JMS transport. It would not work.
+                    </div>
+    </div></div>
+           </div>
+           <!-- Content -->
+         </td>
+        </tr>
+      </table>
+   </td>
+   <td id="cell-2-2" colspan="2">&nbsp;</td>
+  </tr>
+  <tr>
+   <td id="cell-3-0">&nbsp;</td>
+   <td id="cell-3-1">&nbsp;</td>
+   <td id="cell-3-2">
+     <div id="footer">
+       <!-- Footer -->
+       <div id="site-footer">
+         <a href="http://cxf.apache.org/privacy-policy.html">Privacy Policy</a> - 
+         (<a href="https://cwiki.apache.org/confluence/pages/editpage.action?pageId=40509014">edit page</a>) 
+	 (<a href="https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=40509014&amp;showComments=true&amp;showCommentArea=true#addcomment">add comment</a>)<br>
+	Apache CXF, CXF, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.<br>
+        All other marks mentioned may be trademarks or registered trademarks of their respective owners.
+       </div>
+       <!-- Footer -->
+     </div>
+   </td>
+   <td id="cell-3-3">&nbsp;</td>
+   <td id="cell-3-4">&nbsp;</td>
+  </tr>
+  <tr>
+    <td id="cell-4-0" colspan="2">&nbsp;</td>
+    <td id="cell-4-1">&nbsp;</td>
+    <td id="cell-4-2" colspan="2">&nbsp;</td>
+  </tr>
+</table>
+
+<script type="text/javascript">
+var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
+document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
+</script>
+<script type="text/javascript">
+try {
+var pageTracker = _gat._getTracker("UA-4458903-1");
+pageTracker._trackPageview();
+} catch(err) {}</script>
+
+</body>
+</html>
+

Modified: websites/production/cxf/content/docs/jms-transport.html
==============================================================================
--- websites/production/cxf/content/docs/jms-transport.html (original)
+++ websites/production/cxf/content/docs/jms-transport.html Tue Apr 22 12:47:36 2014
@@ -28,15 +28,6 @@
 <meta name="description" content="Apache CXF, Services Framework - JMS Transport">
 
 
-<link type="text/css" rel="stylesheet" href="/resources/highlighter/styles/shCoreCXF.css">
-<link type="text/css" rel="stylesheet" href="/resources/highlighter/styles/shThemeCXF.css">
-
-<script src='/resources/highlighter/scripts/shCore.js'></script>
-<script src='/resources/highlighter/scripts/shBrushJava.js'></script>
-<script>
-  SyntaxHighlighter.defaults['toolbar'] = false;
-  SyntaxHighlighter.all();
-</script>
 
 
     <title>
@@ -116,311 +107,14 @@ Apache CXF -- JMS Transport
          <td height="100%">
            <!-- Content -->
            <div class="wiki-content">
-<div id="ConfluenceContent"><h1 id="JMSTransport-UsingtheJavaMessageService(JMS)">Using the Java Message Service (JMS)</h1>
-
-<p>CXF provides a transport plug-in that enables endpoints to use Java Message Service (JMS) queues and topics. CXF's JMS transport plug-in uses the Java Naming and Directory Interface (JNDI) to locate and obtain references to the JMS provider that brokers for the JMS destinations. Once CXF has established a connection to a JMS provider, CXF supports the passing of messages packaged as either a JMS <code>ObjectMessage</code> or a JMS <code>TextMessage</code>.  The JMS transport also supports the <a shape="rect" class="external-link" href="http://www.w3.org/TR/soapjms/" rel="nofollow">SOAP over JMS specification</a>. See <a shape="rect" href="soap-over-jms-10-support.html">SOAP over JMS 1.0 support</a> for more information.</p>
-
-<p>Standard JMS transport configuration in CXF is done by defining a JMSConduit or JMSDestination, discussed below.  There is however an easier configuration option more conformant to Spring dependency injection, see <a shape="rect" href="using-the-jmsconfigfeature.html">Using the JMSConfigFeature</a>.</p>
-
-<h2 id="JMSTransport-JMSNamespaces">JMS Namespaces</h2>
-
-<h3 id="JMSTransport-WSDLNamespace">WSDL Namespace</h3>
-
-<p>The WSDL extensions for defining a JMS endpoint are defined in the namespace <code><a shape="rect" href="http://cxf.apache.org/transports/jms">http://cxf.apache.org/transports/jms</a></code>. In order to use the JMS extensions you will need to add the namespace definition shown below to the definitions element of your contract.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>JMS Extension Namespace</b></div><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-xmlns:jms=&quot;http://cxf.apache.org/transports/jms&quot;
-]]></script>
-</div></div>
-
-<h3 id="JMSTransport-ConfigurationNamespaces">Configuration Namespaces</h3>
-
-<p>In order to use the JMS configuration properties you will need to add the line shown below to the <code>beans</code> element of your configuration.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>JMS Configuration Namespaces</b></div><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-xmlns:jms=&quot;http://cxf.apache.org/transports/jms&quot;
-]]></script>
-</div></div>
-
-<h2 id="JMSTransport-BasicEndpointConfiguration">Basic Endpoint Configuration</h2>
-
-<p>JMS endpoints need to know certain basic information about how to establish a connection to the proper destination. This information can be provided in one of two places: WSDL or XML configuration. The following configuration elements which are described can be used in both the client side Conduits and the server side Destinations.</p>
-
-<h3 id="JMSTransport-UsingWSDL">Using WSDL</h3>
-
-<p>The JMS destination information is provided using the <code>jms:address</code> element and its child, the <code>jms:JMSNamingProperties</code> element. The <code>jms:address</code> element's attributes specify the information needed to identify the JMS broker and the destination. The <code>jms:JMSNamingProperties</code> element specifies the Java properties used to connect to the JNDI service.</p>
-
-<h4 id="JMSTransport-Theaddresselement">The address element</h4>
-
-<p>The basic configuration for a JMS endpoint is done by using a <code>jms:address</code> element as the child of your service's <code>port</code> element. The <code>jms:address</code> element uses the attributes described below to configure the connection to the JMS broker.</p>
-
-<p><span class="confluence-anchor-link" id="JMSTransport-addressTable"></span></p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Attribute </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>destinationStyle</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Specifies if the JMS destination is a JMS queue or a JMS topic. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>jndiConnectionFactoryName</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Specifies the JNDI name bound to the JMS connection factory to use when connecting to the JMS destination. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>jndiDestinationName</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Specifies the JNDI name bound to the JMS destination to which requests are sent. </p></td></tr><tr><td colspan="1" rowspan
 ="1" class="confluenceTd"><p> <code>jndiReplyDestinationName</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Specifies the JNDI name bound to the JMS destinations where replies are sent. This attribute allows you to use a user defined destination for replies. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>connectionUserName</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Specifies the username to use when connecting to a JMS broker. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>connectionPassword</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Specifies the password to use when connecting to a JMS broker. </p></td></tr></tbody></table></div>
-
-
-<h4 id="JMSTransport-TheJMSNamingPropertieselement">The JMSNamingProperties element</h4>
-
-<p>To increase interoperability with JMS and JNDI providers, the <code>jms:address</code> element has a child element, <code>jms:JMSNamingProperties</code>, that allows you to specify the values used to populate the properties used when connecting to the JNDI provider. The <code>jms:JMSNamingProperties</code> element has two attributes: <code>name</code> and <code>value</code>. The <code>name</code> attribute specifies the name of the property to set. The <code>value</code> attribute specifies the value for the specified property. The <code>jms:JMSNamingProperties</code> element can also be used for specification of provider specific properties.<br clear="none">
-The following is a list of common JNDI properties that can be set:</p>
-<ol><li><code>java.naming.factory.initial</code></li><li><code>java.naming.provider.url</code></li><li><code>java.naming.factory.object</code></li><li><code>java.naming.factory.state</code></li><li><code>java.naming.factory.url.pkgs</code></li><li><code>java.naming.dns.url</code></li><li><code>java.naming.authoritative</code></li><li><code>java.naming.batchsize</code></li><li><code>java.naming.referral</code></li><li><code>java.naming.security.protocol</code></li><li><code>java.naming.security.authentication</code></li><li><code>java.naming.security.principal</code></li><li><code>java.naming.security.credentials</code></li><li><code>java.naming.language</code></li><li><code>java.naming.applet</code></li></ol>
-
-
-<p>For more details on what information to use in these attributes, check your JNDI provider's documentation and consult the Java API reference material.</p>
-
-<h4 id="JMSTransport-Usinganamedreplydestination">Using a named reply destination</h4>
-
-<p>By default, CXF endpoints using JMS create a temporary queue for sending replies back and forth. You can change this behavior by setting the <code>jndiReplyDestinationName</code> attribute in the endpoint's contract. A client endpoint will listen for replies on the specified destination and it will specify the value of the attribute in the <code>ReplyTo</code> field of all outgoing requests. A service endpoint will use the value of the <code>jndiReplyDestinationName</code> attribute as the location for placing replies if there is no destination specified in the request's <code>ReplyTo</code> field.</p>
-
-<p>A static reply queue can not be shared by several instances of the service client. Please use a dynamic reply queue or different queue names per instance instead.</p>
-
-<p>The following example shows an example of a JMS WSDL port specification.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>JMS WSDL Port Specification</b></div><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;service name=&quot;JMSService&quot;&gt;
-  &lt;port binding=&quot;tns:Greeter_SOAPBinding&quot; name=&quot;SoapPort&quot;&gt;
-    &lt;jms:address jndiConnectionFactoryName=&quot;ConnectionFactory&quot;
-                 jndiDestinationName=&quot;dynamicQueues/test.cxf.jmstransport&quot;&gt;
-      &lt;jms:JMSNamingProperty name=&quot;java.naming.factory.initial&quot;
-                             value=&quot;org.apache.activemq.jndi.ActiveMQInitialContextFactory&quot; /&gt;
-      &lt;jms:JMSNamingProperty name=&quot;java.naming.provider.url&quot;
-                             value=&quot;tcp://localhost:61616&quot; /&gt;
-    &lt;/jms:address&gt;
-  &lt;/port&gt;
-&lt;/service&gt;
-]]></script>
-</div></div>
-
-<h3 id="JMSTransport-UsingConfiguration">Using Configuration</h3>
-
-<p>In addition to using the WSDL file to specify the connection information for a JMS endpoint, you can also supply it in the endpoint's XML configuration. The information in the configuration file will override the information in the endpoint's WSDL file.</p>
-
-<h4 id="JMSTransport-Configurationelements">Configuration elements</h4>
-
-<p>You configure a JMS endpoint using one of the following configuration elements:</p>
-<ul><li><strong>jms:conduit</strong>:&#160;The <code>jms:conduit</code> element contains the configuration for a consumer endpoint. It has one attribute, <code>name</code>, whose value takes the form
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>{WSDLNamespace}WSDLPortName.jms-conduit
-</pre>
-</div></div>
-.</li><li><strong>jms:destination</strong>:&#160;The <code>jms:destination</code> element contains the configuration for a provider endpoint. It has one attribute, <code>name</code>, whose value takes the form
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>{WSDLNamespace}WSDLPortName.jms-destination
-</pre>
-</div></div>
-.</li></ul>
-
-
-<h4 id="JMSTransport-Theaddresselement.1">The <code>address</code> element</h4>
-
-<p>JMS connection information is specified by adding a <code>jms:address</code> child to the base configuration element. The <code>jms:address</code> element used in the configuration file is identical to the one used in the WSDL file. Its attributes are listed in the <a shape="rect" href="#JMSTransport-addressTable">address element's attribute table</a>. Like the jms:address element in the WSDL file, the jms:address configuration element also has a <code>jms:JMSNamingProperties</code> child element that is used to specify additional information used to connect to a JNDI provider.</p>
-
-<h4 id="JMSTransport-Example">Example</h4>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Addressing Information a Configuration File</b></div><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;beans xmlns=&quot;http://www.springframework.org/schema/beans&quot;
-       xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
-       xmlns:ct=&quot;http://cxf.apache.org/configuration/types&quot;
-       xmlns:jms=&quot;http://cxf.apache.org/transports/jms&quot;
-       xsi:schemaLocation=&quot;
-           http://www.springframework.org/schema/beans 
-           http://www.springframework.org/schema/beans/spring-beans.xsd
-           http://cxf.apache.org/jaxws
-           http://cxf.apache.org/schemas/jaxws.xsd
-           http://cxf.apache.org/transports/jms
-           http://cxf.apache.org/schemas/configuration/jms.xsd&quot;&gt;
-&lt;jms:conduit name=&quot;{http://cxf.apache.org/jms_endpt}HelloWorldJMSPort.jms-conduit&quot;&gt;
-  &lt;jms:address destinationStyle=&quot;queue&quot;
-               jndiConnectionFactoryName=&quot;myConnectionFactory&quot;
-               jndiDestinationName=&quot;myDestination&quot;
-               jndiReplyDestinationName=&quot;myReplyDestination&quot;
-               connectionUserName=&quot;testUser&quot;
-               connectionPassword=&quot;testPassword&quot;&gt;
-    &lt;jms:JMSNamingProperty name=&quot;java.naming.factory.initial&quot;
-         value=&quot;org.apache.cxf.transport.jms.MyInitialContextFactory&quot;/&gt;
-    &lt;jms:JMSNamingProperty name=&quot;java.naming.provider.url&quot;
-         value=&quot;tcp://localhost:61616&quot;/&gt;
-  &lt;/jms:address&gt;
-&lt;/jms:conduit&gt;
-&lt;/beans&gt;
-]]></script>
-</div></div>
-
-<h3 id="JMSTransport-ConsumerEndpointConfiguration">Consumer Endpoint Configuration</h3>
-
-<p>JMS consumer endpoints specify the type of messages they use. JMS consumer endpoint can use either a JMS <code>ObjectMessage</code> or a JMS <code>TextMessage</code>. When using an <code>ObjectMessage</code> the consumer endpoint uses a <code>byte[]</code> as the method for storing data into and retrieving data from the JMS message body. When messages are sent, the message data, including any formating information, is packaged into a <code>byte[]</code> and placed into the JMS message body before it is placed on the wire. When messages are received, the consumer endpoint will attempt to unmarshall the data stored in the JMS body as if it were packed in a <code>byte[]</code>.</p>
-
-<p>When using a <code>TextMessage</code>, the consumer endpoint uses a string as the method for storing and retrieving data from the JMS message body. When messages are sent, the message information, including any format-specific information, is converted into a string and placed into the JMS message body. When messages are received the consumer endpoint will attempt to unmashall the data stored in the JMS message body as if it were packed into a string.</p>
-
-<p>When native JMS applications interact with CXF consumers, the JMS application is responsible for interpreting the message and the formatting information. For example, if the CXF contract specifies that the binding used for a JMS endpoint is SOAP, and the messages are packaged as <code>TextMessage</code>, the receiving JMS application will get a text message containing all of the SOAP envelope information.</p>
-
-<p>Consumer endpoint can be configured by both XML configuration and via WSDL.</p>
-
-<h3 id="JMSTransport-UsingConfiguration.1">Using Configuration</h3>
-
-
-<h4 id="JMSTransport-Specifyingthemessagetype">Specifying the message type</h4>
-
-<p>You can specify the message type supported by the consumer endpoint using a <code>jms:runtimePolicy</code> element that has a single attribute:</p>
-<ul><li><code>messageType</code> - Specifies how the message data will be packaged as a JMS message. <code>text</code> specifies that the data will be packaged as a <code>TextMessage</code>. <code>binary</code> specifies that the data will be packaged as an <code>ObjectMessage</code>.</li></ul>
-
-
-<p>The following example shows a configuration entry for configuring a JMS consumer endpoint.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Configuration for a JMS Consumer Endpoint</b></div><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;beans xmlns=&quot;http://www.springframework.org/schema/beans&quot;
-       xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
-       xmlns:ct=&quot;http://cxf.apache.org/configuration/types&quot;
-       xmlns:jms=&quot;http://cxf.apache.org/transports/jms&quot;
-       xsi:schemaLocation=&quot;
-           http://www.springframework.org/schema/beans 
-           http://www.springframework.org/schema/beans/spring-beans.xsd&quot;
-           http://cxf.apache.org/jaxws
-           http://cxf.apache.org/schemas/jaxws.xsd
-           http://cxf.apache.org/transports/jms
-           http://cxf.apache.org/schemas/configuration/jms.xsd&quot;&gt;
-...
-&lt;jms:conduit name=&quot;{http://cxf.apache.org/jms_endpt}HelloWorldJMSPort.jms-conduit&quot;&gt;
-  &lt;jms:address ... &gt;
-    ...
-  &lt;/jms:address&gt;
-  &lt;jms:runtimePolicy messageType=&quot;binary&quot;/&gt;
-...
-&lt;/jms:conduit&gt;
-...
-&lt;/beans&gt;
-]]></script>
-</div></div>
-<p>The id on the <code>jms:conduit</code> is in the form of {<code><em>WSDLNamespace</em>}<em>WSDLPortName</em>.jms-conduit</code>. This provides CXF with the information so that it can associate the configuration with your service's endpoint.</p>
-
-<h3 id="JMSTransport-UsingWSDL.1">Using WSDL</h3>
-
-<p>The type of messages accepted by a JMS consumer endpoint is configured using the optional <code>jms:client</code> element. The <code>jms:client</code> element is a child of the WSDL port element and has one attribute:</p>
-<ul><li><code>messageType</code> - Specifies how the message data will be packaged as a JMS message. <code>text</code> specifies that the data will be packaged as a <code>TextMessage</code>. <code>binary</code> specifies that the data will be packaged as an ObjectMessage.</li></ul>
-
-
-<h2 id="JMSTransport-ServiceEndpointConfiguration">Service Endpoint Configuration</h2>
-
-<p>JMS service endpoints have a number of behaviors that are configurable in the contract. These include:</p>
-<ul><li>how messages are correlated</li><li>the use of durable subscriptions</li><li>if the service uses local JMS transactions</li><li>the message selectors used by the endpoint</li></ul>
-
-
-<p>Service endpoints can be configure in one of two ways:</p>
-<ul><li>Configuration</li><li>WSDL</li></ul>
-
-
-<h3 id="JMSTransport-UsingConfiguration.2">Using Configuration</h3>
-
-
-<h4 id="JMSTransport-Specifyingconfigurationdata">Specifying configuration data</h4>
-
-<p>Using the <code>jms:destination</code> elements you can configure your service's endpoint. You can specify the service endpoint's behaviors using the <code>jms:runtimePolicy</code> element that has a the following attributes:</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Attribute </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>useMessageIDAsCorrealationID</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Specifies whether the JMS broker will use the message ID to correlate messages. The default is <code>false</code>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>durableSubscriberName</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Specifies the name used to register a durable subscription. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>messageSelector</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Specifies the string value of a message selector to use. For more information on the syntax used to specify messag
 e <br clear="none" class="atl-forced-newline">
- selectors, see the JMS 1.1 specification. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>transactional</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Specifies whether the local JMS broker will create transactions around message processing. The default is <code>false</code>. </p></td></tr></tbody></table></div>
-
-<p>The following example shows a CXF configuration entry for configuring a JMS service endpoint.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Configuration for a JMS Service Endpoint</b></div><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;beans xmlns=&quot;http://www.springframework.org/schema/beans&quot;
-       xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
-       xmlns:ct=&quot;http://cxf.apache.org/configuration/types&quot;
-       xmlns:jms=&quot;http://cxf.apache.org/transports/jms&quot;
-       xsi:schemaLocation=&quot;
-           http://www.springframework.org/schema/beans
-           http://www.springframework.org/schema/beans/spring-beans.xsd&quot;
-           http://cxf.apache.org/jaxws
-           http://cxf.apache.org/schemas/jaxws.xsd
-           http://cxf.apache.org/transports/jms
-           http://cxf.apache.org/schemas/configuration/jms.xsd&quot;&gt;
-...
-&lt;jms:destination name=&quot;{http://cxf.apache.org/jms_endpt}HelloWorldJMSPort.jms-destination&quot;&gt;
-  &lt;jms:address ... &gt;
-    ...
-  &lt;/jms:address&gt;
-  ...
-  &lt;jms:runtimePolicy messageSelector=&quot;cxf_message_selector&quot;
-       useMessageIDAsCorrelationID=&quot;true&quot;
-       transactional=&quot;true&quot;
-       durableSubscriberName=&quot;cxf_subscriber&quot; /&gt;
-  ...
-&lt;/jms:destination&gt;
-...
-&lt;/beans&gt;
-]]></script>
-</div></div>
-
-<h3 id="JMSTransport-UsingWSDL.2">Using WSDL</h3>
-
-<p>Service endpoint behaviors are configured using the optional <code>jms:server</code> element. The <code>jms:server</code> element is a child of the WSDL <code>port</code> element and has the following attributes:</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Attribute </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>useMessageIDAsCorrealationID</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Specifies whether JMS will use the message ID to correlate messages. The default is <code>false</code>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>durableSubscriberName</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Specifies the name used to register a durable subscription. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>messageSelector</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Specifies the string value of a message selector to use. For more information on the syntax used to specify message <br clear
 ="none" class="atl-forced-newline">
- selectors, see the JMS 1.1 specification. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>transactional</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Specifies whether the local JMS broker will create transactions around message processing. The default is <code>false</code>. Currently, this is not supported by the runtime. </p></td></tr></tbody></table></div>
-
-
-<h2 id="JMSTransport-JMSRuntimeConfiguration">JMS Runtime Configuration</h2>
-
-<p>In addition to configuring the externally visible aspects of your JMS endpoint, you can also configure aspects of its internal runtime behavior. There are three types of runtime configuration:</p>
-<ul><li>Session pool configuration (common to both services and consumers)</li><li>Consumer specific configuration</li><li>Service specific configuration</li></ul>
-
-
-<h3 id="JMSTransport-SessionPoolConfiguration">Session Pool Configuration</h3>
-
-<p>You configure an endpoint's JMS session pool using the <code>jms:sessionPoolConfig</code> element. This property allows you to set a high and low water mark for the number of JMS sessions an endpoint will keep pooled. The endpoint is guaranteed to maintain a pool of sessions equal to the low water mark and to never pool more sessions than specified by the high water mark.<br clear="none">
-The <code>jms:sessionPool</code> element's attributes, listed below, specify the high and low water marks for the endpoint's JMS session pool.</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Attribute </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>lowWaterMark</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Specifies the minimum number of JMS sessions pooled by the endpoint. The default is 20. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>highWaterMark</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Specifies the maximum number of JMS sessions pooled by the endpoint. The default is 500. </p></td></tr></tbody></table></div>
-
-<p>The following example shows an example of configuring the session pool for a CXF JMS service endpoint.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>JMS Session Pool Configuration</b></div><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;jms:destination 
-   name=&quot;{http://cxf.apache.org/jms_endpit}HelloWorldJMSPort.jms-destination&quot;&gt;
-...
-  &lt;jms:sessionPool lowWaterMark=&quot;10&quot; highWaterMark=&quot;5000&quot; /&gt;
-&lt;/jms:destination&gt;
-]]></script>
-</div></div>
-<p>The <code>jms:sessionPool</code> element can also be used within a <code>jms:conduit</code>.</p>
-
-<h3 id="JMSTransport-ConsumerSpecificRuntimeConfiguration">Consumer Specific Runtime Configuration</h3>
-
-<p>The JMS consumer configuration allows you to specify two runtime behaviors:</p>
-<ul><li>the number of milliseconds the consumer will wait for a response.</li><li>the number of milliseconds a request will exist before the JMS broker can remove it.</li></ul>
-
-
-<p>You use the <code>jms:clientConfig</code> element to set JMS consumer runtime behavior. This element's attributes, listed in the following table, specify the configuration values for consumer runtime behavior.</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Attribute </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>clientReceiveTimeout</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Specifies the amount of time, in milliseconds, that the endpoint will wait for a response before it times out and issues an exception. The default value is 2000. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>messageTimeToLive</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Specifies the amount of time, in milliseconds, that a request can remain unrecieved before the JMS broker can delete it. The default value is 0 which specifies that the message can never be deleted. </p></td></tr></tbody></table></div>
-
-<p>The following example shows a configuration fragment that sets the consumer endpoint's request lifetime to 500 milliseconds and its timeout value to 500 milliseconds.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>JMS Consumer Endpoint Runtime Configuration</b></div><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;jms:conduit name=&quot;{http://cxf.apache.org/jms_endpt}HelloWorldJMSPort.jms-conduit&quot;&gt;
-...
-  &lt;jms:clientConfig clientReceiveTimeout=&quot;500&quot;
-                    messageTimeToLive=&quot;500&quot; /&gt;
-&lt;/jms:conduit&gt;
-]]></script>
-</div></div>
-
-<h3 id="JMSTransport-ServiceSpecificRuntimeConfiguration">Service Specific Runtime Configuration</h3>
-
-<p>The JMS service configuration allows you to specify to runtime behaviors:</p>
-<ul><li>the amount of time a response message can remain unreceived before the JMS broker can delete it.</li><li>the client identifier used when creating and accessing durable subscriptions.</li></ul>
-
-
-<p>The <code>jms:serverConfig</code> element is used to specify the service runtime configuration. This element's attributes, listed below, specify the configuration values that control the service's runtime behavior.</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Attribute </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>messageTimeToLive</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Specifies the amount of time, in milliseconds, that a response can remain unread before the JMS broker is allowed to delete it. The default is 0 which specifies that the message can live forever. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>durableSubscriptionClientId</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Specifies the client identifier the endpoint uses to create and access durable subscriptions. </p></td></tr></tbody></table></div>
-
-<p>The following example shows a configuration fragment that sets the service endpoint's response lifetime to 500 milliseconds and its durable subscription client identifier to <code>jms-test-id</code>.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>JMS Service Endpoint Runtime Configuration</b></div><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;jms:destination id=&quot;{http://cxf.apache.org/jms_endpt}HelloWorldJMSPort.jms-destination&quot;&gt;
-  &lt;jms:address ... &gt;
-    ...
-  &lt;/jms:address&gt;
-  &lt;jms:serverConfig messageTimeToLive=&quot;500&quot;
-                    durableSubscriptionClientId=&quot;jms-test-id&quot; /&gt;
-&lt;/jms:destination&gt;
-]]></script>
-</div></div></div>
+<div id="ConfluenceContent"><h1 id="JMSTransport-UsingtheJavaMessageService(JMS)">Using the Java Message Service (JMS)</h1><p>CXF provides a transport plug-in that enables endpoints to use Java Message Service (JMS) queues and topics. CXF's JMS transport plug-in uses the Java Naming and Directory Interface (JNDI) to locate and obtain references to the JMS provider that brokers for the JMS destinations. Once CXF has established a connection to a JMS provider, CXF supports the passing of messages packaged as either a JMS <code>ObjectMessage</code> or a JMS <code>TextMessage</code>. The JMS transport also supports the <a shape="rect" class="external-link" href="http://www.w3.org/TR/soapjms/" rel="nofollow">SOAP over JMS specification</a>. See <a shape="rect" href="soap-over-jms-10-support.html">SOAP over JMS 1.0 support</a> for more information.</p><h2 id="JMSTransport-Configurationstyles">Configuration styles</h2><ul><li><a shape="rect" href="soap-over-jms-10-support.html">SOAP / JMS 
 spec compliant configuration</a> - recommended style for CXF 3</li><li><a shape="rect" href="using-the-jmsconfigfeature.html">JMSConfiguration style</a> - works in CXF 2 and 3 but is deprecated for CXF 3</li><li><a shape="rect" href="cxf-2x-jms-configuration-removed-in-cxf-3.html">CXF 2.x JMS configuration</a><span class="confluence-link"> - removed in CXF 3</span></li></ul><h2 id="JMSTransport-Advancedexamples(CXF&gt;=3)">Advanced examples (CXF &gt;= 3)</h2><ul><li><a shape="rect" href="jms-performance-and-pooling.html">Performance and pooling</a></li><li><a shape="rect" href="jms-transactions.html">JMS transactions</a></li></ul><h2 id="JMSTransport-Reconnectfunctionality">Reconnect functionality</h2><p>The JMS transport automatically reconnects when any JMS exceptions happen. The first exception will be logged with "Exception on JMS connection. Trying to reconnect" and the exception details.<br clear="none">Then CXF will try to reconnect every 5 seconds and log "Exception on recon
 nect. Trying again, attempt num x".</p><p>In conduits every exception when sending a message will be thrown to the caller. The conduit then closes the connection and will start a new one when sending the next message.</p>    <div class="aui-message problem shadowed information-macro">
+                    <p class="title">Reconnects and pooling</p>
+                            <span class="aui-icon icon-problem">Icon</span>
+                <div class="message-content">
+                            <p>When using pooling make sure the pool throws away the Connection in case of errors. In ActiveMQ PooledConnection this can be achieved using setExpiryTimeout(milliseconds).</p>
+                    </div>
+    </div>
+<p>In CXF 2.x the JMS server must be present before JMS endpoints are started. In cxf 3 the endpoint will start and periodically reconnect like in the case of an exception while running.</p><p>&#160;</p></div>
            </div>
            <!-- Content -->
          </td>



Mime
View raw message