[
https://issues.apache.org/jira/browse/CXF-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14048999#comment-14048999
]
Daniel Kulp commented on CXF-5831:
----------------------------------
Part of setting the ValidationEventHandler on the marshaller WAS exactly to
make it a little more strict that JAXB is by default. We had many many many
support requests wondering why there data was coming in as null or not being
parsed or similar. Setting a simple EventHandler on the marshaller provides
some information about the validity of the message without incurring any
additional processing overhead that full schema validation incurs.
You can turn this off by setting the contextual property
"set-jaxb-validation-event-handler" to false.
> WSUIDValidationHandler is more strict than default behavior of JAXB
> -------------------------------------------------------------------
>
> Key: CXF-5831
> URL: https://issues.apache.org/jira/browse/CXF-5831
> Project: CXF
> Issue Type: Bug
> Components: JAXB Databinding
> Affects Versions: 2.7.11, 3.0.0
> Reporter: Kyle Lape
> Fix For: Invalid
>
>
> Looking at the code and CXF-3453, it doesn't appear that the
> {{WSUIDValidationHandler}} was intended to make CXF more strict in rejecting
> validation events, e.g. extra elements within SOAP body or empty string
> values for {{xs:int}}. Since that {{ValidationEventHandler}} returns
> {{false}} by default, it causes JAXB to halt processing on various events
> that it wouldn't by default.
> Could we only install the {{WSUIDValidationHandler}} when schema validation
> and (maybe) WS-Security are enabled?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
