You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Jason Pell (JIRA)" <ji...@apache.org> on 2012/11/03 09:20:12 UTC
[jira] [Created] (CXF-4610) Provide support for enabling /
disabling Schema Validation at the Operation level
Jason Pell created CXF-4610:
-------------------------------
Summary: 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
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
[jira] [Updated] (CXF-4610) Provide support for enabling /
disabling Schema Validation at the Operation level
Posted by "Jason Pell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Pell updated CXF-4610:
----------------------------
Fix Version/s: 2.7.1
> 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
[jira] [Updated] (CXF-4610) Provide support for enabling /
disabling Schema Validation at the Operation level
Posted by "Jason Pell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Pell updated CXF-4610:
----------------------------
Attachment: (was: patch.txt)
> 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
[jira] [Updated] (CXF-4610) Provide support for enabling /
disabling Schema Validation at the Operation level
Posted by "Jason Pell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Pell updated CXF-4610:
----------------------------
Comment: was deleted
(was: Initial patch - I will commit this myself, just putting it here for reference until i get a chance to do a full build to ensure no checkstyle, other breaks.
This patch is only fully supported in JAX-WS. Its activated via the DocLiteralInInterceptor and AbstractDataOutInterceptor.
Because it should work for all data bindings out going I need to look at how I might either disable for other data bindings or add the necessary changes to the other bindings as well.
)
> 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
[jira] [Updated] (CXF-4610) Provide support for enabling /
disabling Schema Validation at the Operation level
Posted by "Jason Pell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Pell updated CXF-4610:
----------------------------
Attachment: patch.txt
Initial patch - I will commit this myself, just putting it here for reference until i get a chance to do a full build to ensure no checkstyle, other breaks.
This patch is only fully supported in JAX-WS. Its activated via the DocLiteralInInterceptor and AbstractDataOutInterceptor.
Because it should work for all data bindings out going I need to look at how I might either disable for other data bindings or add the necessary changes to the other bindings as well.
> 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
> Attachments: patch.txt
>
>
> 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
[jira] [Assigned] (CXF-4610) Provide support for enabling /
disabling Schema Validation at the Operation level
Posted by "Jason Pell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Pell reassigned CXF-4610:
-------------------------------
Assignee: Jason Pell
> 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
>
> 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
[jira] [Commented] (CXF-4610) Provide support for enabling /
disabling Schema Validation at the Operation level
Posted by "Jason Pell (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Resolved] (CXF-4610) Provide support for enabling /
disabling Schema Validation at the Operation level
Posted by "Jason Pell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Pell resolved CXF-4610.
-----------------------------
Resolution: Fixed
> 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