Author: buildbot
Date: Thu Apr 12 10:48:08 2012
New Revision: 812515
Log:
Production update by buildbot for cxf
Modified:
websites/production/cxf/content/cache/docs.pageCache
websites/production/cxf/content/docs/jax-rs-client-api.html
Modified: websites/production/cxf/content/cache/docs.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/cxf/content/docs/jax-rs-client-api.html
==============================================================================
--- websites/production/cxf/content/docs/jax-rs-client-api.html (original)
+++ websites/production/cxf/content/docs/jax-rs-client-api.html Thu Apr 12
10:48:08 2012
@@ -280,7 +280,7 @@ BusFactory.setDefaultBus(bus);
<h2><a shape="rect" name="JAX-RSClientAPI-Limitations"></a>Limitations</h2>
-<p>Proxy methods can not have @Context method parameters and subresource
methods returning Objects can not be invoked. This is perhaps not much of a
problem, as you can inject contexts as field or bean properties and have
subresource methods returning typed classes: interfaces, abstract classes or
concrete implementations. </p>
+<p>Proxy sub-resource methods returning Objects can not be invoked. Prefer to
have sub-resource methods returning typed classes: interfaces, abstract classes
or concrete implementations. </p>
<p>When a proxy method returning a JAX-RS Response is invoked, the returned
Response.getEntity() will return a response InputStream by default. Starting
with CXF 2.3.2 one can register an org.apache.cxf.jaxrs.client.ResponseReader
provider and cast the Response.getEntity() to more specific application
classes:</p>
