Author: buildbot
Date: Fri Jan 11 10:48:05 2013
New Revision: 846118
Log:
Production update by buildbot for cxf
Modified:
websites/production/cxf/content/cache/docs.pageCache
websites/production/cxf/content/docs/bus-configuration.html
websites/production/cxf/content/docs/configuration.html
Modified: websites/production/cxf/content/cache/docs.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/cxf/content/docs/bus-configuration.html
==============================================================================
--- websites/production/cxf/content/docs/bus-configuration.html (original)
+++ websites/production/cxf/content/docs/bus-configuration.html Fri Jan 11
10:48:05 2013
@@ -123,13 +123,13 @@ Apache CXF -- Bus Configuration
<div class="wiki-content">
<div id="ConfluenceContent"><h1><a shape="rect"
name="BusConfiguration-ConfiguringtheBus"></a>Configuring the Bus</h1>
-<p>The Bus is the backbone of CXF architecture. It manages extensions and acts
as an interceptor provider. The interceptors for the bus will be added to the
respective inbound and outbound message and fault interceptor chains for all
client and server endpoints created on the bus (in its context). By default,
it contributes no interceptors to either of these interceptor chain types, but
they can be added via configuration files or with Java code, as shown below.</p>
+<p>The Bus is the backbone of the CXF architecture. It manages extensions and
acts as an interceptor provider. The interceptors for the bus will be added to
the respective inbound and outbound message and fault interceptor chains for
all client and server endpoints created on the bus (in its context). By
default, it contributes no interceptors to either of these interceptor chain
types, but they can be added via configuration files or with Java code, as
shown below.</p>
<p>Note: For endpoint-specific configuration (as opposed to configuration for
<b>all</b> for endpoints created by the CXF bus), look at the <a shape="rect"
href="debugging-and-logging.html" title="Debugging and Logging">Logging
Messages</a> section for code samples.</p>
<h3><a shape="rect" name="BusConfiguration-UsingaConfigurationFile"></a>Using
a Configuration File</h3>
-<p>Here, simply define a bus element in your Spring configuration file, and
add child elements as required,for example:</p>
+<p>Here, simply define a bus element in your Spring configuration file, and
add child elements as required, for example:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-xml">
@@ -151,8 +151,7 @@ http://www.springframework.org/schema/be
</pre>
</div></div>
-<p>The configurable properties of the bus are defined in the bus configuration
schema <a shape="rect" class="external-link"
href="http://svn.apache.org/viewvc/cxf/trunk/rt/core/src/main/resources/schemas/core.xsd?view=markup";>http://cxf.apache.org/schemas/core.xsd</a>.<br
clear="none">
-Be sure to include the namespace - URI pair for this schema in the
schemaLocation attribute of the <beans> element.</p>
+<p>The configurable properties of the bus are defined in the bus configuration
schema <a shape="rect" class="external-link"
href="http://svn.apache.org/viewvc/cxf/trunk/rt/core/src/main/resources/schemas/core.xsd?view=markup";>http://cxf.apache.org/schemas/core.xsd</a>.
Be sure to include the namespace - URI pair for this schema in the
schemaLocation attribute of the <beans> element.</p>
<p>The <bus> element supports the following child elements:</p>
@@ -163,8 +162,7 @@ Be sure to include the namespace - URI p
<h3><a shape="rect"
name="BusConfiguration-ConfigurationusingJavacode"></a>Configuration using Java
code</h3>
-<p>Although usually less convenient, interceptors can be added to the bus
using Java code. Given an <a shape="rect"
href="http://cxf.apache.org/javadoc/latest/org/apache/cxf/jaxws/EndpointImpl.html";>EndpointImpl</a>
object, the<br clear="none">
-bus can be accessed (and interceptors added) as follows:</p>
+<p>Although usually less convenient, interceptors can be added to the bus
using Java code. Given an <a shape="rect"
href="http://cxf.apache.org/javadoc/latest/org/apache/cxf/jaxws/EndpointImpl.html";>EndpointImpl</a>
object, the bus can be accessed (and interceptors added) as follows:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-java">
Modified: websites/production/cxf/content/docs/configuration.html
==============================================================================
--- websites/production/cxf/content/docs/configuration.html (original)
+++ websites/production/cxf/content/docs/configuration.html Fri Jan 11 10:48:05
2013
@@ -122,7 +122,6 @@ Apache CXF -- Configuration
<!-- Content -->
<div class="wiki-content">
<div id="ConfluenceContent"><h1><a shape="rect"
name="Configuration-Configuration"></a>Configuration</h1>
-<p>...</p>
<h2><a shape="rect" name="Configuration-Subpages"></a>Subpages</h2>
<ul><li><a shape="rect" href="bus-configuration.html" title="Bus
Configuration">Bus Configuration</a></li><li><a shape="rect"
href="featureslist.html" title="FeaturesList">FeaturesList</a></li><li><a
shape="rect" href="jmx-management.html" title="JMX Management">JMX
Management</a></li><li><a shape="rect" href="wsaconfiguration.html"
title="WSAConfiguration">WSAConfiguration</a></li><li><a shape="rect"
href="wspconfiguration.html"
title="WSPConfiguration">WSPConfiguration</a></li><li><a shape="rect"
href="wsrmconfiguration.html"
title="WSRMConfiguration">WSRMConfiguration</a></li></ul>
@@ -206,6 +205,8 @@ In some cases it also possible to achiev
<p><b>Enabling message logging using plain Spring bean elements</b></p>
+<div class="panelMacro"><table class="noteMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle"
src="https://cwiki.apache.org/confluence/images/icons/emoticons/warning.gif";
width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1">Using
this format is STRONGLY discouraged as it ties your configuration with internal
CXF class names (like SpringBus). It is much better to use the cxf:bus element
described below</td></tr></table></div>
+
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-xml">
<beans xmlns=<span
class="code-quote">"http://www.springframework.org/schema/beans";</span>
@@ -242,10 +243,7 @@ http://www.springframework.org/schema/be
</pre>
</div></div>
-<p>In this example, you specify that the CXF bus is implemented by class
org.apache.cxf.bus.spring.SpringBus, and that it's id is "cxf". This is the
default, but you have to re-iterate the fact if you want the bus to contribute
the logging interceptors to the outbound and inbound interceptor chain for all
client and server endpoints. You can avoid this duplication by using the next
form of configuration:</p>
-
-<div class="panelMacro"><table class="noteMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle"
src="https://cwiki.apache.org/confluence/images/icons/emoticons/warning.gif";
width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1">Using
this format is STRONGLY discouraged as it ties your configuration with internal
CXF class names (like SpringBus). It is much better to use the cxf:bus element
described below</td></tr></table></div>
-
+<p>In this example, you specify that the CXF bus is implemented by class
org.apache.cxf.bus.spring.SpringBus, and that its id is "cxf". This is the
default, but you have to re-iterate the fact if you want the bus to contribute
the logging interceptors to the outbound and inbound interceptor chain for all
client and server endpoints. You can avoid this duplication by using the next
form of configuration:</p>
<p><b>Enabling message logging using custom CXF bean elements</b></p>
![https://cwiki.apache.org/confluence/images/icons/emoticons/warning.gif"](https://cwiki.apache.org/confluence/images/icons/emoticons/warning.gif"){kind=link}