cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Redko (Confluence)" <conflue...@apache.org>
Subject [CONF] Apache CXF Documentation > ValidationFeature
Date Sat, 30 Nov 2013 19:31:00 GMT
<html>
<head>
    <base href="https://cwiki.apache.org/confluence">
            <link rel="stylesheet" href="/confluence/s/en/2176/1/1/_/styles/combined.css?spaceKey=CXF20DOC&amp;forWysiwyg=true"
type="text/css">
    </head>
<body style="background: white;" bgcolor="white" class="email-body">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
    <h2><a href="https://cwiki.apache.org/confluence/display/CXF20DOC/ValidationFeature">ValidationFeature</a></h2>
    <h4>Page <b>edited</b> by             <a href="https://cwiki.apache.org/confluence/display/~reta">Andrew
Redko</a>
    </h4>
        <br/>
                         <h4>Changes (1)</h4>
                                 
    
<div id="page-diffs">
                    <table class="diff" cellpadding="0" cellspacing="0">
    
            <tr><td class="diff-snipped" >...<br></td></tr>
            <tr><td class="diff-unchanged" >sf.create(); <br>{code} <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">
<br>h2. Configuring Bean Validation 1.1 using Spring bean definitions XML <br>
<br>Following the similar approach as for JAXRSServerFactoryBean, in case of Spring
respective bean definitions should be added under &lt;jaxrs:outInterceptors&gt;, &lt;jaxrs:inInterceptors&gt;
and &lt;jaxrs:providers&gt; sections, f.e.: <br>{code} <br>&lt;jaxrs:server
address=&quot;/&quot;&gt; <br>    &lt;jaxrs:inInterceptors&gt; <br>
       &lt;ref bean=&quot;validationInInterceptor&quot; /&gt; <br> 
  &lt;/jaxrs:inInterceptors&gt; <br> <br>    &lt;jaxrs:outInterceptors&gt;
<br>        &lt;ref bean=&quot;validationOutInterceptor&quot; /&gt;
<br>    &lt;/jaxrs:outInterceptors&gt; <br> <br>    &lt;jaxrs:serviceBeans&gt;
<br>    ... <br>    &lt;/jaxrs:serviceBeans&gt; <br> <br>
   &lt;jaxrs:providers&gt; <br>        &lt;ref bean=&quot;exceptionMapper&quot;/&gt;
<br>    &lt;/jaxrs:providers&gt; <br>&lt;/jaxrs:server&gt; <br>
<br>&lt;bean id=&quot;exceptionMapper&quot; class=&quot;org.apache.cxf.jaxrs.validation.ValidationExceptionMapper&quot;/&gt;
<br>&lt;bean id=&quot;validationProvider&quot; class=&quot;org.apache.cxf.validation.BeanValidationProvider&quot;
/&gt; <br> <br>&lt;bean id=&quot;validationInInterceptor&quot;
class=&quot;org.apache.cxf.jaxrs.validation.JAXRSBeanValidationInInterceptor&quot;&gt;
<br>    &lt;property name=&quot;provider&quot; ref=&quot;validationProvider&quot;
/&gt; <br>&lt;/bean&gt; <br> <br>&lt;bean id=&quot;validationOutInterceptor&quot;
class=&quot;org.apache.cxf.jaxrs.validation.JAXRSBeanValidationOutInterceptor&quot;&gt;
<br>    &lt;property name=&quot;provider&quot; ref=&quot;validationProvider&quot;
/&gt; <br>&lt;/bean&gt;    <br>{code} <br> <br>h2. Validation
Exceptions and HTTP status codes <br> <br>As per JAX-RS 2.0 specification, any
input parameter validation violation is mapped to HTTP status code 400 Bad Request and any
return value validation violation (or internal validation violation) is mapped to HTTP status
code 500 Internal Server Error. This is essentially what org.apache.cxf.jaxrs.validation.ValidationExceptionMapper
does. <br>{note} <br>At the moment, the details of validation exceptions are not
included into the response. The reason why is that error reporting logic is application-specific
and may vary from application to application (f.e. it could be simple &#39;text/html&#39;
with error message, or &#39;application/json&#39;, or HTTP custom headers, ...). Application
developers are encouraged to provide own implementation of this particular functionality.
<br>{note} <br></td></tr>
    
            </table>
    </div>                            <h4>Full Content</h4>
                    <div class="notificationGreySide">
        <p><span style="font-size:2em;font-weight:bold"> Bean Validation Feature
</span></p>

<div>
<ul>
<ul>
    <li><a href='#ValidationFeature-Introduction'>Introduction</a></li>
    <li><a href='#ValidationFeature-Dependencies'>Dependencies</a></li>
<ul>
    <li><a href='#ValidationFeature-UsingHibernateValidatorasbeanvalidationprovider'>Using
Hibernate Validator as bean validation provider</a></li>
    <li><a href='#ValidationFeature-UsingApacheBValasbeanvalidationprovider'>Using
Apache BVal as bean validation provider</a></li>
</ul>
</ul>
    <li><a href='#ValidationFeature-BeanValidation1.1andJAXRS2.0integration'>Bean
Validation 1.1 and JAX-RS 2.0 integration</a></li>
<ul>
    <li><a href='#ValidationFeature-ConfiguringBeanValidation1.1usingJAXRSServerFactoryBean'>Configuring
Bean Validation 1.1 using JAXRSServerFactoryBean</a></li>
    <li><a href='#ValidationFeature-ConfiguringBeanValidation1.1usingSpringbeandefinitionsXML'>Configuring
Bean Validation 1.1 using Spring bean definitions XML</a></li>
    <li><a href='#ValidationFeature-ValidationExceptionsandHTTPstatuscodes'>Validation
Exceptions and HTTP status codes</a></li>
</ul>
</ul></div>

<h2><a name="ValidationFeature-Introduction"></a>Introduction</h2>
<p>Among many other features, JAX-RS 2.0 specification introduces Bean Validation 1.1
support as a mandatory part of implementation. In an effort to fulfill this requirement, Apache
CXF provides full-fledge validation support for JAX-RS / JAX-WS endpoints, both for request
parameters and response values.</p>

<h2><a name="ValidationFeature-Dependencies"></a>Dependencies</h2>
<p>Bean Validation support in Apache CXF is implementation-independent and is built
solely using API. As such, the only required dependency is:</p>
<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent
panelContent">
<pre>&lt;dependency&gt;
    &lt;groupId&gt;javax.validation&lt;/groupId&gt;
    &lt;artifactId&gt;validation-api&lt;/artifactId&gt;
    &lt;version&gt;1.1.0.Final&lt;/version&gt;
&lt;/dependency&gt;
</pre>
</div></div>

<p>API doesn't provide implementation but there are couple of choices to pick from.
Please notice that bean validation implementation is taken from the ones present in classpath.
If no implementation is detected, bean validation is not available for use and constraints
validation won't have any effect. </p>

<h3><a name="ValidationFeature-UsingHibernateValidatorasbeanvalidationprovider"></a>Using
Hibernate Validator as bean validation provider</h3>
<p><a href="http://www.hibernate.org/subprojects/validator.html" class="external-link"
rel="nofollow">http://www.hibernate.org/subprojects/validator.html</a></p>

<p>Hibernate Validator is mature and feature-rich validation provider with full support
of Bean Validation 1.1 (as of version 5.x.x which is the reference implementation for JSR
349 - Bean Validation 1.1 API). To use Hibernate Validator in your Apache CXF projects, couple
of additional dependencies should be included:</p>

<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent
panelContent">
<pre>&lt;dependency&gt;
    &lt;groupId&gt;org.hibernate&lt;/groupId&gt;
    &lt;artifactId&gt;hibernate-validator&lt;/artifactId&gt;
    &lt;version&gt;5.0.1.Final&lt;/version&gt;
&lt;/dependency&gt;

&lt;dependency&gt;
    &lt;groupId&gt;javax.el&lt;/groupId&gt;
    &lt;artifactId&gt;javax.el-api&lt;/artifactId&gt;
    &lt;version&gt;3.0-b02&lt;/version&gt;
&lt;/dependency&gt;

&lt;dependency&gt;
    &lt;groupId&gt;org.glassfish&lt;/groupId&gt;
    &lt;artifactId&gt;javax.el&lt;/artifactId&gt;
    &lt;version&gt;3.0-b01/version&gt;
&lt;/dependency&gt;
</pre>
</div></div>

<p>Hibernate Validator uses Java Expression Language 3.0 in order to provide better
validation messages support so the respective EL 3.0 API and implementation dependencies should
be included.  </p>

<h3><a name="ValidationFeature-UsingApacheBValasbeanvalidationprovider"></a>Using
Apache BVal as bean validation provider</h3>
<p><a href="http://bval.apache.org/" class="external-link" rel="nofollow">http://bval.apache.org/</a></p>

<p>Current stable version of Apache BVal (0.5) doesn't support Bean Validation 1.1 but
the upcoming 1.1.0 should have it fully implemented (at the moment 1.1.0-alpha-SNAPSHOT could
be used).</p>
<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent
panelContent">
<pre>&lt;dependency&gt;
    &lt;groupId&gt;org.apache.bval&lt;/groupId&gt;
    &lt;artifactId&gt;bval-jsr&lt;/artifactId&gt;
    &lt;version&gt;1.1.0-alpha-SNAPSHOT&lt;/version&gt;
&lt;/dependency&gt;
</pre>
</div></div>

<h1><a name="ValidationFeature-BeanValidation1.1andJAXRS2.0integration"></a>Bean
Validation 1.1 and JAX-RS 2.0 integration</h1>

<p>Bean Validation 1.1 support in JAX-RS 2.0 is built on top of three main components:</p>
<ul class="alternate" type="square">
	<li>in-interceptor (org.apache.cxf.jaxrs.validation.JAXRSBeanValidationInInterceptor):
validates REST/WS endpoint parameters before invoking the method</li>
	<li>out-interceptor (org.apache.cxf.jaxrs.validation.JAXRSBeanValidationOutInterceptor):
validates REST/WS endpoint return value after the method invocation</li>
	<li>exception mapper (org.apache.cxf.jaxrs.validation.ValidationExceptionMapper): transforms
any ValidationException to corresponding HTTP status code</li>
</ul>


<p>All these components may share the single instance of org.apache.cxf.validation.BeanValidationProvider
which actually delegates all validation logic to available Bean Validation 1.1 implementation.</p>

<h2><a name="ValidationFeature-ConfiguringBeanValidation1.1usingJAXRSServerFactoryBean"></a>Configuring
Bean Validation 1.1 using JAXRSServerFactoryBean</h2>

<p>It's quite easy to enable bean validation support using JAXRSServerFactoryBean as
following code snippet shows:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="theme: Default; brush: java; gutter: false" style="font-size:12px; font-family:
ConfluenceInstalledFont,monospace;">
JAXRSServerFactoryBean sf = new JAXRSServerFactoryBean();
sf.setResourceClasses( ... );
sf.setResourceProvider( ... );
sf.setProvider(new ValidationExceptionMapper());
sf.setInInterceptors(Arrays.&lt; Interceptor&lt; ? extends Message &gt; &gt;asList(new
new JAXRSBeanValidationInInterceptor()));
sf.setOutInterceptors(Arrays.&lt; Interceptor&lt; ? extends Message &gt; &gt;asList(new
JAXRSBeanValidationOutInterceptor()));
sf.create();
</pre>
</div></div>

<h2><a name="ValidationFeature-ConfiguringBeanValidation1.1usingSpringbeandefinitionsXML"></a>Configuring
Bean Validation 1.1 using Spring bean definitions XML</h2>

<p>Following the similar approach as for JAXRSServerFactoryBean, in case of Spring respective
bean definitions should be added under &lt;jaxrs:outInterceptors&gt;, &lt;jaxrs:inInterceptors&gt;
and &lt;jaxrs:providers&gt; sections, f.e.:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="theme: Default; brush: java; gutter: false" style="font-size:12px; font-family:
ConfluenceInstalledFont,monospace;">
&lt;jaxrs:server address="/"&gt;
    &lt;jaxrs:inInterceptors&gt;
        &lt;ref bean="validationInInterceptor" /&gt;
    &lt;/jaxrs:inInterceptors&gt;
        
    &lt;jaxrs:outInterceptors&gt;
        &lt;ref bean="validationOutInterceptor" /&gt;
    &lt;/jaxrs:outInterceptors&gt;
        
    &lt;jaxrs:serviceBeans&gt;
    ...
    &lt;/jaxrs:serviceBeans&gt;
        
    &lt;jaxrs:providers&gt;
        &lt;ref bean="exceptionMapper"/&gt;
    &lt;/jaxrs:providers&gt;
&lt;/jaxrs:server&gt;

&lt;bean id="exceptionMapper" class="org.apache.cxf.jaxrs.validation.ValidationExceptionMapper"/&gt;
&lt;bean id="validationProvider" class="org.apache.cxf.validation.BeanValidationProvider"
/&gt;

&lt;bean id="validationInInterceptor" class="org.apache.cxf.jaxrs.validation.JAXRSBeanValidationInInterceptor"&gt;
    &lt;property name="provider" ref="validationProvider" /&gt;
&lt;/bean&gt;

&lt;bean id="validationOutInterceptor" class="org.apache.cxf.jaxrs.validation.JAXRSBeanValidationOutInterceptor"&gt;
    &lt;property name="provider" ref="validationProvider" /&gt;
&lt;/bean&gt;   
</pre>
</div></div>

<h2><a name="ValidationFeature-ValidationExceptionsandHTTPstatuscodes"></a>Validation
Exceptions and HTTP status codes</h2>

<p>As per JAX-RS 2.0 specification, any input parameter validation violation is mapped
to HTTP status code 400 Bad Request and any return value validation violation (or internal
validation violation) is mapped to HTTP status code 500 Internal Server Error. This is essentially
what org.apache.cxf.jaxrs.validation.ValidationExceptionMapper does.</p>
<div class='panelMacro'><table class='noteMacro'><colgroup><col width='24'><col></colgroup><tr><td
valign='top'><img src="/confluence/images/icons/emoticons/warning.gif" width="16" height="16"
align="absmiddle" alt="" border="0"></td><td>At the moment, the details of
validation exceptions are not included into the response. The reason why is that error reporting
logic is application-specific and may vary from application to application (f.e. it could
be simple 'text/html' with error message, or 'application/json', or HTTP custom headers, ...).
Application developers are encouraged to provide own implementation of this particular functionality.</td></tr></table></div>
    </div>
        <div id="commentsSection" class="wiki-content pageSection">
        <div style="float: right;" class="grey">
                        <a href="https://cwiki.apache.org/confluence/users/removespacenotification.action?spaceKey=CXF20DOC">Stop
watching space</a>
            <span style="padding: 0px 5px;">|</span>
                <a href="https://cwiki.apache.org/confluence/users/editmyemailsettings.action">Change
email notification preferences</a>
</div>
        <a href="https://cwiki.apache.org/confluence/display/CXF20DOC/ValidationFeature">View
Online</a>
        |
        <a href="https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=34842111&revisedVersion=4&originalVersion=3">View
Changes</a>
            </div>
</div>
</div>
</div>
</div>
</body>
</html>

Mime
View raw message