svn commit: r1027368 - in /websites/production/cxf/content: cache/docs.pageCache docs/sse.html

[buildbot]

Author: buildbot
Date: Mon Mar 26 00:05:49 2018
New Revision: 1027368

Log:
Production update by buildbot for cxf

Modified:
    websites/production/cxf/content/cache/docs.pageCache
    websites/production/cxf/content/docs/sse.html

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

Modified: websites/production/cxf/content/docs/sse.html
==============================================================================
--- websites/production/cxf/content/docs/sse.html (original)
+++ websites/production/cxf/content/docs/sse.html Mon Mar 26 00:05:49 2018
@@ -33,6 +33,7 @@
 
 <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/shBrushBash.js'></script>
 <script>
   SyntaxHighlighter.defaults['toolbar'] = false;
@@ -127,7 +128,35 @@ holder.setInitParameter(CXFCdiServlet.TR
 factory.setTransportId(SseHttpTransportFactory.TRANSPORT_ID);
 ...
 return factory.create();</pre>
-</div></div><h2 id="SSE-AdvancedConfiguration">Advanced 
Configuration</h2><p>Since <strong>Apache CXF 3.2.3</strong> release, it is 
possible to use alternative means to configure transports, including SSE one, 
by passing it through the <strong>Bus</strong> property "<a shape="rect" 
class="external-link" href="http://org.apache.cxf.preferred.transport.id"; 
rel="nofollow">org.apache.cxf.preferred.transport.id</a>" (also available as 
<strong>AbstractTransportFactory.PREFERRED_TRANSPORT_ID</strong> constant). 
With this property set to preferred transport, CXF servlet in question is going 
to pick it up instead of using the default one. SSE implementation benefits 
from that and in many cases setting the <strong>"transportId" </strong>init 
parameter on the servlet level could be omitted.</p><p>&#160;</p></div>
+</div></div><h2 id="SSE-AdvancedConfiguration">Advanced 
Configuration</h2><p>Since <strong>Apache CXF 3.2.3</strong> release, it is 
possible to use alternative means to configure transports, including SSE one, 
by passing it through the <strong>Bus</strong> property "<a shape="rect" 
class="external-link" href="http://org.apache.cxf.preferred.transport.id"; 
rel="nofollow">org.apache.cxf.preferred.transport.id</a>" (also available as 
<strong>AbstractTransportFactory.PREFERRED_TRANSPORT_ID</strong> constant). 
With this property set to preferred transport, CXF servlet in question is going 
to pick it up instead of using the default one. SSE implementation benefits 
from that and in many cases setting the <strong>"transportId" </strong>init 
parameter on the servlet level could be omitted.</p><h2 
id="SSE-OSGi">OSGi</h2><p>For the deployments inside OSGi containers (like 
Apache Karaf), <strong>Apache CXF</strong> provides a dedicated 
<strong>cxf-sse</strong> feature (which depends on <strong>c
 xf-http</strong> and <strong>cxf-jaxrs</strong>).</p><div class="preformatted 
panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
+<pre>karaf@root()&gt; feature:install cxf-sse </pre>
+</div></div><p>Once installed, the dependent bundles could benefit from SSE 
capabilities by specifying desired transport in the Blueprint configuration, 
for example.</p><div class="code panel pdl" style="border-width: 1px;"><div 
class="codeContent panelContent pdl">
+<pre class="brush: java; gutter: false; theme: Default" 
style="font-size:12px;">&lt;blueprint 
xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0";
+       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
+       xmlns:cxf="http://cxf.apache.org/blueprint/core";
+       xmlns:jaxrs="http://cxf.apache.org/blueprint/jaxrs";
+
+       xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0 
http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
+                           http://cxf.apache.org/blueprint/core 
http://cxf.apache.org/schemas/blueprint/core.xsd
+                           http://cxf.apache.org/jaxrs 
http://cxf.apache.org/schemas/blueprint/jaxrs.xsd"&gt;
+
+    &lt;cxf:bus&gt;
+        &lt;cxf:features&gt;
+            &lt;cxf:logging /&gt;
+        &lt;/cxf:features&gt;
+    &lt;/cxf:bus&gt;
+
+    &lt;jaxrs:server id="sseSampleService" address="/" 
transportId="http://cxf.apache.org/transports/http/sse"&gt;
+        &lt;jaxrs:serviceBeans&gt;
+            &lt;ref component-id="..." /&gt;
+        &lt;/jaxrs:serviceBeans&gt;
+        &lt;jaxrs:providers&gt;
+            &lt;ref component-id="..." /&gt;
+        &lt;/jaxrs:providers&gt;
+    &lt;/jaxrs:server&gt;
+
+&lt;/blueprint&gt;</pre>
+</div></div></div>
            </div>
            <!-- Content -->
          </td>