You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cxf.apache.org by bu...@apache.org on 2012/12/04 15:48:10 UTC
svn commit: r840726 - in /websites/production/cxf/content:
cache/docs.pageCache docs/jax-rs-data-bindings.html
Author: buildbot
Date: Tue Dec 4 14:48:09 2012
New Revision: 840726
Log:
Production update by buildbot for cxf
Modified:
websites/production/cxf/content/cache/docs.pageCache
websites/production/cxf/content/docs/jax-rs-data-bindings.html
Modified: websites/production/cxf/content/cache/docs.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/cxf/content/docs/jax-rs-data-bindings.html
==============================================================================
--- websites/production/cxf/content/docs/jax-rs-data-bindings.html (original)
+++ websites/production/cxf/content/docs/jax-rs-data-bindings.html Tue Dec 4 14:48:09 2012
@@ -423,6 +423,12 @@ If Moxy is used to handle beans without
<p>One may want to use the "singleJaxbContext" property in combination with the "skipChecks" property if it is known that only valid JAXB beans will be read or written.</p>
+<p>Also note that setting only "extraClass", without setting "singleJaxbContext" property will also work in cases when no package JAXB contexts are created (specifically when no ObjectFactory or jaxb.index have been found). Starting from CXF 2.7.2 and 2.6.4 it will also work well for package contexts. </p>
+
+<p>However, when possible, prefer always setting both "singleJaxbContext" and "extraClass" properties. Starting from CXF 2.7.2 this will also work well for package-level contexts - add "useSingleContextForPackages" property to get the created single context always used as a package context.</p>
+
+
+
<h2><a shape="rect" name="JAX-RSDataBindings-AutomaticJAXBElementconversionduringserialization"></a>Automatic JAXBElement conversion during serialization</h2>
<p>In some cases, wrapping object instances into JAXBElements may affect the way XML is produced. For example, given Base and Derived classes, returning an instance of Derived class, with Base one being a method response type, would produce an additional xsi:type attribute if this instance is wrapped into JAXBElement. One can set a "jaxbElementClassNames" list property which can contain class names like "org.foo.Base", etc.</p>