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

[bu...@apache.org]

Author: buildbot
Date: Sat Mar  3 19:56:39 2018
New Revision: 1026233

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 Sat Mar  3 19:56:39 2018
@@ -127,7 +127,7 @@ holder.setInitParameter(CXFCdiServlet.TR
 factory.setTransportId(SseHttpTransportFactory.TRANSPORT_ID);
 ...
 return factory.create();</pre>
-</div></div></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><p>&#160;</p></div>
            </div>
            <!-- Content -->
          </td>