cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Pell (JIRA)" <>
Subject [jira] [Commented] (CXF-4610) Provide support for enabling / disabling Schema Validation at the Operation level
Date Thu, 29 Nov 2012 09:26:58 GMT


Jason Pell commented on CXF-4610:

The original intention was to support this at the JAX-WS level.  I am going to mark the issue
as resolved and open a new issue to deal with the other data bindings.
> Provide support for enabling / disabling Schema Validation at the Operation level
> ---------------------------------------------------------------------------------
>                 Key: CXF-4610
>                 URL:
>             Project: CXF
>          Issue Type: New Feature
>          Components: JAX-WS Runtime
>    Affects Versions: 2.7.0
>            Reporter: Jason Pell
>            Assignee: Jason Pell
>             Fix For: 2.7.1
> This functionality would make it possible to enable schema validation for specific operations
in a java first SEI.  The feature should support using the SchemaValidation annotation on
methods instead of just at class level.
> However it would also be beneficial to be able to do something similiar to the DomainExpression
functionality for ws-policy.
> So on an endpoint (or globally for all end points) define a SchemaValidationExpression
interface something like:
> public interface SchemaValidationExpression {
>     boolean appliesTo(BindingMessageInfo bmi);
>     boolean appliesTo(BindingOperationInfo boi);
> }
> This would make it possible to control whether validation occurs on an operation as a
whole, or whether it occurs on just the IN or the OUT message, just like for ws-policy DomainExpression.
> I require this functionality for the project I work on, and will investigate how at least
the SchemaValidation annotation functionality at the operation level can be implemented.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message