Author: buildbot
Date: Mon Apr 9 17:48:11 2012
New Revision: 812087
Log:
Production update by buildbot for cxf
Modified:
websites/production/cxf/content/cache/docs.pageCache
websites/production/cxf/content/docs/26-migration-guide.html
websites/production/cxf/content/docs/annotations.html
Modified: websites/production/cxf/content/cache/docs.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/cxf/content/docs/26-migration-guide.html
==============================================================================
--- websites/production/cxf/content/docs/26-migration-guide.html (original)
+++ websites/production/cxf/content/docs/26-migration-guide.html Mon Apr 9
17:48:11 2012
@@ -123,7 +123,7 @@ Apache CXF -- 2.6 Migration Guide
<div class="wiki-content">
<div id="ConfluenceContent"><h3><a shape="rect"
name="2.6MigrationGuide-NewFeatures"></a>New Features</h3>
-<ul><li>The big OSGi bundle used in the Karaf features.xml has been replaced
with the individual modules which are now all individual bundles. The big
OSGi bundle is still built, but some features may not be available if that is
used instead of the little bundles.</li><li>New ability to configure HTTP
Conduits from the OSGi config:admin service</li><li>New ability to configure
the CXF created HTTP Jetty ports from config:admin service</li><li>OAuth 2
support (new cxf-rt-rs-security-oauth2 module)</li><li>The STS now supports the
Renewal binding for SAML tokens.</li><li>The STS also supports bulk
issuing/validation/cancelling/renewal of security tokens.</li><li>The STS
supports some advanced features based around Claims, such as Claims
Transformation, and pluggable custom Claims Parsing.</li><li>The WS-Security
module now supports replay detection by default of Timestamps and UsernameToken
nonces.</li><li>New ability to register custom JAX-RS Context
providers.</li></ul>
+<ul><li>The big OSGi bundle used in the Karaf features.xml has been replaced
with the individual modules which are now all individual bundles. The big
OSGi bundle is still built, but some features may not be available if that is
used instead of the little bundles.</li><li>New ability to configure HTTP
Conduits from the OSGi config:admin service</li><li>New ability to configure
the CXF created HTTP Jetty ports from config:admin service</li><li>OAuth 2
support (new cxf-rt-rs-security-oauth2 module)</li><li>The STS now supports the
Renewal binding for SAML tokens.</li><li>The STS also supports bulk
issuing/validation/cancelling/renewal of security tokens.</li><li>The STS
supports some advanced features based around Claims, such as Claims
Transformation, and pluggable custom Claims Parsing.</li><li>The WS-Security
module now supports replay detection by default of Timestamps and UsernameToken
nonces.</li><li>New ability to register custom JAX-RS Context
providers.</li><li>New
<a shape="rect"
href="annotations.html#Annotations-UseAsyncMethod">@UseAsyncMethod</a>
annotation for JAX-WS services.</li></ul>
<h3><a shape="rect" name="2.6MigrationGuide-RemovedModules"></a>Removed
Modules</h3>
Modified: websites/production/cxf/content/docs/annotations.html
==============================================================================
--- websites/production/cxf/content/docs/annotations.html (original)
+++ websites/production/cxf/content/docs/annotations.html Mon Apr 9 17:48:11
2012
@@ -274,6 +274,42 @@ Apache CXF -- Annotations
}
</pre>
+</div></div>
+
+<p><a shape="rect" name="Annotations-Policy"></a></p>
+<h3><a shape="rect"
name="Annotations-org.apache.cxf.annotations.UseAsyncMethod%28since2.6.0%29"></a>org.apache.cxf.annotations.UseAsyncMethod
(since 2.6.0)</h3>
+<p>Used on the JAX-WS service implementation object to mark a method as
preferring the 'async' version of the method instead of the synchronous
version. With JAX-WS, services default to the synchronous methods that
require the returning value to be returned from the method. By marking a
method with the @UseAsyncMethod annotation, if the transport supports it, CXF
will call the async version that takes an AsynHandler object and the service
can call that handler when the response is ready. If the transport does not
support the CXF continuations, the synchronous method will be called as
normal.</p>
+
+<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
+<pre class="code-java">
+
+ @UseAsyncMethod
+ <span class="code-keyword">public</span> <span
class="code-object">String</span> greetMeSometime(<span
class="code-object">String</span> me) {
+ LOG.info(<span class="code-quote">"Executing operation greetMeSometime
synchronously"</span>);
+ <span class="code-object">System</span>.out.println(<span
class="code-quote">"Executing operation greetMeSometime
synchronously\n"</span>);
+ <span class="code-keyword">return</span> <span class="code-quote">"How
are you "</span> + me;
+ }
+
+ <span class="code-keyword">public</span> Future<?>
greetMeSometimeAsync(<span class="code-keyword">final</span> <span
class="code-object">String</span> me,
+ <span
class="code-keyword">final</span> AsyncHandler<GreetMeSometimeResponse>
asyncHandler) {
+ LOG.info(<span class="code-quote">"Executing operation
greetMeSometimeAsync asynchronously"</span>);
+ <span class="code-object">System</span>.out.println(<span
class="code-quote">"Executing operation greetMeSometimeAsync
asynchronously\n"</span>);
+ <span class="code-keyword">final</span>
ServerAsyncResponse<GreetMeSometimeResponse> r
+ = <span class="code-keyword">new</span>
ServerAsyncResponse<GreetMeSometimeResponse>();
+ <span class="code-keyword">new</span> <span
class="code-object">Thread</span>() {
+ <span class="code-keyword">public</span> void run() {
+ GreetMeSometimeResponse resp = <span
class="code-keyword">new</span> GreetMeSometimeResponse();
+ resp.setResponseType(<span class="code-quote">"How are you
"</span> + me);
+ r.set(resp);
+ <span class="code-object">System</span>.out.println(<span
class="code-quote">"Responding on background thread\n"</span>);
+ asyncHandler.handleResponse(r);
+ }
+ } .start();
+
+ <span class="code-keyword">return</span> r;
+ }
+
+</pre>
</div></div></div>
</div>
<!-- Content -->
