cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r835633 - in /websites/production/cxf/content: cache/docs.pageCache docs/jms-transport.html docs/using-the-jmsconfigfeature.html
Date Fri, 19 Oct 2012 17:47:37 GMT
Author: buildbot
Date: Fri Oct 19 17:47:37 2012
New Revision: 835633

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/using-the-jmsconfigfeature.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 Fri Oct 19 17:47:37 2012
@@ -123,19 +123,12 @@ Apache CXF -- JMS Transport
            <div class="wiki-content">
 <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>
+<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>.
 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"
title="SOAP over JMS 1.0 support">SOAP over JMS 1.0 support</a> for more information.</p>
 
-<h2><a shape="rect" name="JMSTransport-EasierconfigurationusingthenewJMSConfigFeature"></a>Easier
configuration using the new JMSConfigFeature</h2>
-
-<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-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>
+<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"
title="Using the JMSConfigFeature">Using the JMSConfigFeature</a>.</p>
 
 <h2><a shape="rect" name="JMSTransport-JMSNamespaces"></a>JMS Namespaces</h2>
 
-
 <h3><a shape="rect" name="JMSTransport-WSDLNamespace"></a>WSDL Namespace</h3>
 
 <p>The WSDL extensions for defining a JMS endpoint are defined in the namespace <tt><a
shape="rect" href="http://cxf.apache.org/transports/jms">http://cxf.apache.org/transports/jms</a></tt>.
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>
@@ -185,7 +178,7 @@ The following is a list of common JNDI p
 
 <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 <tt>jndiReplyDestinationName</tt>
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 <tt>ReplyTo</tt>
field of all outgoing requests. A service endpoint will use the value of the <tt>jndiReplyDestinationName</tt>
attribute as the location for placing replies if there is no destination specified in the
request's <tt>ReplyTo</tt> field.</p>
 
-<p>As of CXF 2.1.3 and 2.0.9 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. (<a shape="rect" class="external-link" href="http://www.nabble.com/CXF-2.1.3-JMS-Conduit-to20447067.html"
rel="nofollow">See discussion on the mailing list</a>)</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" style="border-width: 1px;"><div class="codeHeader panelHeader"
style="border-bottom-width: 1px;"><b>JMS WSDL Port Specification</b></div><div
class="codeContent panelContent">

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 Fri Oct 19 17:47:37
2012
@@ -121,7 +121,7 @@ Apache CXF -- Using the JMSConfigFeature
          <td height="100%">
            <!-- Content -->
            <div class="wiki-content">
-<div id="ConfluenceContent"><p>In older CXF version the JMS transport is configured
by defining a JMSConduit or JMSDestination. Starting with CXF 2.0.9 and 2.1.3 the JMS transport
includes an easier configuration option that is more conformant to the spring dependency injection.
Additionally the new configuration has much more options. For example it is not necessary
anymore to use JNDI to resolve the connection factory. Instead it can be defined in the spring
config.</p>
+<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>
 



Mime
View raw message