[
https://issues.apache.org/jira/browse/CXF-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466667#comment-13466667
]
Jason Pell edited comment on CXF-3813 at 10/1/12 6:14 PM:
----------------------------------------------------------
I am assuming I need to maintain backwards compatibility with the enabled field
from SchemaValidation annotation interface as well? If thats the case then I
have the following code in AnnotationsFactoryBeanListener
Oops - my bad you can't have a null default value for a field in an annotation.
So I will have to think of another way to support both.
was (Author: pellcorp):
I am assuming I need to maintain backwards compatibility with the enabled
field from SchemaValidation annotation interface as well? If thats the case
then I have the following code in AnnotationsFactoryBeanListener
private void addSchemaValidationSupport(Endpoint endpoint, SchemaValidation
annotation) {
if (annotation != null) {
if (annotation.type() != null) {
endpoint.put(Message.SCHEMA_VALIDATION_ENABLED,
annotation.type().name());
} else {
endpoint.put(Message.SCHEMA_VALIDATION_ENABLED,
annotation.enabled());
}
}
}
> Possibiblity to only validate requests and/or responses
> -------------------------------------------------------
>
> Key: CXF-3813
> URL: https://issues.apache.org/jira/browse/CXF-3813
> Project: CXF
> Issue Type: Improvement
> Components: JAX-WS Runtime
> Affects Versions: 2.4.2
> Environment: N/A
> Reporter: David J. M. Karlsen
> Labels: cxf, schema, validation, xsd
>
> Today it is possible to specify to validate or not, it would be even better
> if one could specify to only validate requests, only responses, or both as
> today.
--
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