Return-Path: X-Original-To: apmail-cxf-issues-archive@www.apache.org Delivered-To: apmail-cxf-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 58A1FD350 for ; Thu, 29 Nov 2012 09:27:01 +0000 (UTC) Received: (qmail 75424 invoked by uid 500); 29 Nov 2012 09:27:01 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 75012 invoked by uid 500); 29 Nov 2012 09:27:00 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 74602 invoked by uid 99); 29 Nov 2012 09:26:58 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Nov 2012 09:26:58 +0000 Date: Thu, 29 Nov 2012 09:26:58 +0000 (UTC) From: "Jason Pell (JIRA)" To: issues@cxf.apache.org Message-ID: <1491542466.39168.1354181218509.JavaMail.jiratomcat@arcas> In-Reply-To: <675771699.64507.1351930812629.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (CXF-4610) Provide support for enabling / disabling Schema Validation at the Operation level MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CXF-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506355#comment-13506355 ] 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: https://issues.apache.org/jira/browse/CXF-4610 > 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: http://www.atlassian.com/software/jira