cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r833095 - in /websites/production/cxf/content: cache/docs.pageCache docs/jms-transport.html docs/transports.html
Date Wed, 26 Sep 2012 18:47:27 GMT
Author: buildbot
Date: Wed Sep 26 18:47:26 2012
New Revision: 833095

Log:
Production update by buildbot for cxf

Modified:
    websites/production/cxf/content/cache/docs.pageCache
    websites/production/cxf/content/docs/jms-transport.html
    websites/production/cxf/content/docs/transports.html

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

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 Wed Sep 26 18:47:26 2012
@@ -121,7 +121,7 @@ Apache CXF -- JMS Transport
          <td height="100%">
            <!-- Content -->
            <div class="wiki-content">
-<div id="ConfluenceContent"><h1><a shape="rect" name="JMSTransport-UsingtheJavaMessageService"></a>Using
the Java Message Service</h1>
+<div id="ConfluenceContent"><h1><a shape="rect" name="JMSTransport-UsingtheJavaMessageService%28JMS%29"></a>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 <tt>ObjectMessage</tt> or a JMS <tt>TextMessage</tt>.</p>
 
@@ -129,7 +129,7 @@ Apache CXF -- JMS Transport
 
 <p>Starting with CXF 2.0.9 and 2.1.3 there is a new easier and more flexible configuration
style available. See <a shape="rect" href="using-the-jmsconfigfeature.html" title="Using
the JMSConfigFeature">Using the JMSConfigFeature</a></p>
 
-<h2><a shape="rect" name="JMSTransport-JMSTransportwihtSOAPoverJavaMessageService1.0Supported"></a>JMS
Transport wiht SOAP over Java Message Service 1.0-Supported </h2>
+<h2><a shape="rect" name="JMSTransport-JMSTransportwithSOAPoverJavaMessageService1.0Supported"></a>JMS
Transport with SOAP over Java Message Service 1.0-Supported </h2>
 
 <p>Starting with the CXF 2.3, we make some improvement on the JMS Transport to support
<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"
title="SOAP over JMS 1.0 support">SOAP over JMS 1.0 support</a> for more information.</p>
 

Modified: websites/production/cxf/content/docs/transports.html
==============================================================================
--- websites/production/cxf/content/docs/transports.html (original)
+++ websites/production/cxf/content/docs/transports.html Wed Sep 26 18:47:26 2012
@@ -122,7 +122,7 @@ Apache CXF -- Transports
            <!-- Content -->
            <div class="wiki-content">
 <div id="ConfluenceContent"><h1><a shape="rect" name="Transports-Transports"></a>Transports</h1>
-<p>CXF include support for several transport protocols including HTTP, Servlet, JMS,
In-VM and many others via the Camel transport for CXF such as SMTP/POP3, TCP and Jabber. CXF
transport implementation is also flexible and provides the possibility to add own custom transport.</p>
+<p>CXF include support for several transport protocols including HTTP, Servlet, JMS,
UDP, In-VM and many others via the Camel transport for CXF such as SMTP/POP3, TCP and Jabber.
CXF transport implementation is also flexible and provides the possibility to add own custom
transport.</p>
 
 <ul><li><a shape="rect" href="apache-camel-transport.html" title="Apache Camel
Transport">Apache Camel Transport</a></li><li><a shape="rect" href="coloc-feature.html"
title="Coloc Feature">Coloc Feature</a></li><li><a shape="rect" href="custom-transport.html"
title="Custom Transport">Custom Transport</a></li><li><a shape="rect"
href="http-transport.html" title="HTTP Transport">HTTP Transport</a><ul><li><a
shape="rect" href="client-http-transport-including-ssl-support.html" title="Client HTTP Transport
(including SSL support)">Client HTTP Transport (including SSL support)</a></li><li><a
shape="rect" href="jetty-configuration.html" title="Jetty Configuration">Jetty Configuration</a></li><li><a
shape="rect" href="server-http-transport.html" title="Server HTTP Transport">Server HTTP
Transport</a></li><li><a shape="rect" href="servlet-transport.html" title="Servlet
Transport">Servlet Transport</a></li><li><a shape="rect" href="standalone-http-transport.html"
title="Standalone HTT
 P Transport">Standalone HTTP Transport</a></li></ul></li><li><a
shape="rect" href="jms-transport.html" title="JMS Transport">JMS Transport</a><ul><li><a
shape="rect" href="soap-over-jms-10-support.html" title="SOAP over JMS 1.0 support">SOAP
over JMS 1.0 support</a></li><li><a shape="rect" href="using-the-jmsconfigfeature.html"
title="Using the JMSConfigFeature">Using the JMSConfigFeature</a></li></ul></li><li><a
shape="rect" href="local-transport.html" title="Local Transport">Local Transport</a></li></ul></div>
            </div>



Mime
View raw message