You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cxf.apache.org by bu...@apache.org on 2012/09/19 12:47:28 UTC
svn commit: r832449 - in /websites/production/cxf/content:
cache/docs.pageCache docs/custom-transport.data/cxf-transport.jpg
docs/custom-transport.html
Author: buildbot
Date: Wed Sep 19 10:47:27 2012
New Revision: 832449
Log:
Production update by buildbot for cxf
Added:
websites/production/cxf/content/docs/custom-transport.data/cxf-transport.jpg (with props)
Modified:
websites/production/cxf/content/cache/docs.pageCache
websites/production/cxf/content/docs/custom-transport.html
Modified: websites/production/cxf/content/cache/docs.pageCache
==============================================================================
Binary files - no diff available.
Added: websites/production/cxf/content/docs/custom-transport.data/cxf-transport.jpg
==============================================================================
Binary file - no diff available.
Propchange: websites/production/cxf/content/docs/custom-transport.data/cxf-transport.jpg
------------------------------------------------------------------------------
svn:mime-type = image/jpeg
Modified: websites/production/cxf/content/docs/custom-transport.html
==============================================================================
--- websites/production/cxf/content/docs/custom-transport.html (original)
+++ websites/production/cxf/content/docs/custom-transport.html Wed Sep 19 10:47:27 2012
@@ -141,7 +141,7 @@ To send a message into a physical channe
<h2><a shape="rect" name="CustomTransport-HowitWorks"></a>How it Works</h2>
<p>Interaction between JAX-WS client and service using CXF transport is represented in the following figure:<br clear="none">
-<span class="image-wrap" style=""><img src="custom-transport.data/cxf-transport-view.jpg" style="border: 0px solid black"></span></p>
+<span class="image-wrap" style=""><img src="custom-transport.data/cxf-transport.jpg" style="border: 0px solid black"></span></p>
<h3><a shape="rect" name="CustomTransport-SimplifiedClientWorkflow%3A"></a>Simplified Client Workflow:</h3>
@@ -239,7 +239,7 @@ serviceClass=<span class="code-quote">"o
<p>It is strongly recommended to don’t break streaming in Conduit and Destination implementations, if physical protocol supports it. CXF is completely streaming oriented – it causes high performance and scalability.</p>
<h2><a shape="rect" name="CustomTransport-References"></a>References</h2>
-<p>What is the start point to understand the CXF transport layer and implement own transport? I would recommend to read CXF documentation <span class="error">[CXF transports overview#http://cxf.apache.org/docs/transports.html]</span> and analyze source code of existing CXF transports (Local and JMS once are more straightforward). They are located into packages: org.apache.cxf.transport.local and org.apache.cxf.transport.jms correspondingly</p>
+<p>What is the start point to understand the CXF transport layer and implement own transport? It makes sense to read CXF documentation <a shape="rect" href="http://cxf.apache.org/docs/transports.html">CXF transports overview</a> and analyze source code of existing CXF transports (Local and JMS once are more straightforward). They are located into packages: org.apache.cxf.transport.local and org.apache.cxf.transport.jms correspondingly.</p>
</div>
</div>
<!-- Content -->