cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r963281 - in /websites/production/cxf/content: cache/docs.pageCache docs/jax-rs.html
Date Thu, 27 Aug 2015 17:47:26 GMT
Author: buildbot
Date: Thu Aug 27 17:47:25 2015
New Revision: 963281

Log:
Production update by buildbot for cxf

Modified:
    websites/production/cxf/content/cache/docs.pageCache
    websites/production/cxf/content/docs/jax-rs.html

Modified: websites/production/cxf/content/cache/docs.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/cxf/content/docs/jax-rs.html
==============================================================================
--- websites/production/cxf/content/docs/jax-rs.html (original)
+++ websites/production/cxf/content/docs/jax-rs.html Thu Aug 27 17:47:25 2015
@@ -118,11 +118,11 @@ Apache CXF -- JAX-RS
            <!-- Content -->
            <div class="wiki-content">
 <div id="ConfluenceContent"><p>&#160;</p><p>&#160;<span
class="inline-first-p" style="font-size:2em;font-weight:bold">JAX-RS (JSR-339)</span>&#160;</p><p>&#160;</p><p><style
type="text/css">/*<![CDATA[*/
-div.rbtoc1439570813071 {padding: 0px;}
-div.rbtoc1439570813071 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1439570813071 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1440697613222 {padding: 0px;}
+div.rbtoc1440697613222 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1440697613222 li {margin-left: 0px;padding-left: 0px;}
 
-/*]]>*/</style></p><div class="toc-macro rbtoc1439570813071">
+/*]]>*/</style></p><div class="toc-macro rbtoc1440697613222">
 <ul class="toc-indentation"><li><a shape="rect" href="#JAX-RS-Introduction">Introduction</a></li><li><a
shape="rect" href="#JAX-RS-JAX-RSCompliance">JAX-RS Compliance</a>
 <ul class="toc-indentation"><li><a shape="rect" href="#JAX-RS-1.1">1.1</a></li><li><a
shape="rect" href="#JAX-RS-2.0Final">2.0 Final</a></li></ul>
 </li><li><a shape="rect" href="#JAX-RS-Projectsetupandconfiguration">Project
setup and configuration</a>
@@ -202,7 +202,7 @@ public void upload(InputStream is) {
 public void upload(@Multipart InputStream is) {
 }
 </pre>
-</div></div><p>Alternatively, setting a "support.type.as.multipart" contextual
property will do.</p><p>7. If the custom code throws JAX-RS WebApplicationException
with Response containing a non-null entity then custom WebApplicationException mappers will
be bypassed - another problematic requirement, for example, the custom mappers doing the logging
will miss on such exceptions.<br clear="none"> Set CXF "support.wae.spec.optimization"
property to false to disable it.</p><p>8. In some cases the matching sub-resource
locators will be dropped to precisely meet the current JAX-RS matching algorithm text, please
see <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/CXF-5650">CXF-5650</a>
for more information. Use a new "keep.subresource.candidates" property to support the existing
application if needed.</p><h3 id="JAX-RS-CXF3.1.2ProviderSortingChanges">CXF 3.1.2
Provider Sorting Changes</h3><p>Starting from CXF 3.1.2 custom MessageBodyReader
(MBR) and Mess
 ageBodyWriter (MBW) providers are sorted together with default providers.</p><p>Before
CXF 3.1.2 if a custom MBR or MBW matches the read or write selection criteria, example, if
MBR Consumes matches Content-Type and its isReadable() returns true, then</p><p>the
default providers are not even checked. The specification however does let the custom providers
be selected only if no higher priority matching default provider is available.</p><p>For
example, suppose you have a custom StringReader which is not typed by String but by Object.
In this case the default provider which is typed by String wins. To have the custom String
provider winning one needs to type it by String. Check the specification or ask at the users
list for more details</p><h3 id="JAX-RS-FromCXF2.6.xtoCXF2.7.x">From CXF 2.6.x
to CXF 2.7.x</h3><p>Please check the <a shape="rect" href="http://cxf.apache.org/docs/27-migration-guide.html">CXF
2.7 Migration Guide</a> for the information about all the changes affecting the 
 JAX-RS users</p><h2 id="JAX-RS-Mavendependencies">Maven dependencies</h2><h3
id="JAX-RS-CXF3.0.0">CXF 3.0.0</h3><p>The cxf-rt-frontend-jaxrs dependency
is required:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+</div></div><p>Alternatively, setting a "support.type.as.multipart" contextual
property will do.</p><p>7. If the custom code throws JAX-RS WebApplicationException
with Response containing a non-null entity then custom WebApplicationException mappers will
be bypassed - another problematic requirement, for example, the custom mappers doing the logging
will miss on such exceptions.<br clear="none"> Set CXF "support.wae.spec.optimization"
property to false to disable it.</p><p>8. In some cases the matching sub-resource
locators will be dropped to precisely meet the current JAX-RS matching algorithm text, please
see <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/CXF-5650">CXF-5650</a>
for more information. Use a new "keep.subresource.candidates" property to support the existing
application if needed.</p><h3 id="JAX-RS-CXF3.1.2ProviderSortingChanges">CXF 3.1.2
Provider Sorting Changes</h3><p>Starting from CXF 3.1.2 customMessageBodyReader
(MBR), MessageB
 odyWriter (MBW) and ExceptionMapper providers are sorted together with default providers.</p><p>Before
CXF 3.1.2 if a custom MBR or MBW matches the read or write selection criteria, example, if
MBR Consumes matches Content-Type and its isReadable() returns true, then</p><p>the
default providers are not even checked. The specification however does let the custom providers
be selected only if no higher priority matching default provider is available.</p><p>For
example, suppose you have a custom StringReader which is not typed by String but by Object.
In this case the default provider which is typed by String wins. To have the custom String
provider winning one needs to type it by String.</p><p>Check the specification
or ask at the users list for more details.</p><h3 id="JAX-RS-FromCXF2.6.xtoCXF2.7.x">From
CXF 2.6.x to CXF 2.7.x</h3><p>Please check the <a shape="rect" href="http://cxf.apache.org/docs/27-migration-guide.html">CXF
2.7 Migration Guide</a> for the information about all the
  changes affecting the JAX-RS users</p><h2 id="JAX-RS-Mavendependencies">Maven
dependencies</h2><h3 id="JAX-RS-CXF3.0.0">CXF 3.0.0</h3><p>The cxf-rt-frontend-jaxrs
dependency is required:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
 <pre class="brush: xml; gutter: false; theme: Default" style="font-size:12px;">   &lt;dependency&gt;
       &lt;groupId&gt;org.apache.cxf&lt;/groupId&gt;
       &lt;artifactId&gt;cxf-rt-frontend-jaxrs&lt;/artifactId&gt;



Mime
View raw message