Author: buildbot
Date: Fri Oct 5 22:47:25 2012
New Revision: 834190
Log:
Production update by buildbot for cxf
Modified:
websites/production/cxf/content/cache/docs.pageCache
websites/production/cxf/content/docs/jaxrs-services-configuration.html
Modified: websites/production/cxf/content/cache/docs.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/cxf/content/docs/jaxrs-services-configuration.html
==============================================================================
--- websites/production/cxf/content/docs/jaxrs-services-configuration.html
(original)
+++ websites/production/cxf/content/docs/jaxrs-services-configuration.html Fri
Oct 5 22:47:25 2012
@@ -364,6 +364,8 @@ http://cxf.apache.org/schemas/jaxrs.xsd";
</pre>
</div></div>
+<p>In the above configuration all resources will be configured as singletons,
see <a shape="rect"
href="#JAXRSServicesConfiguration-JAXRSServicesConfigurationFromSpring">below</a>
for information on creating per-request resources.</p>
+
<h1><a shape="rect"
name="JAXRSServicesConfiguration-ConfiguringJAXRSservicesusingexplicitbeanconfiguration"></a>Configuring
JAX-RS services using explicit bean configuration</h1>
<p>Note that jaxrs:server (and jaxrs:client) declarations depend on
'http://cxf.apache.org/jaxrs' Spring NamespaceHandler be available on
classpath. Sometimes, due to classloading restrictions or bugs in underlying
containers which are exposed during complex deployments or due to multiple
Spring libraries interfering with each other, NamespaceHandler can not be
located and thus jaxrs endpoints can not be created. <br clear="none">
