[
https://issues.apache.org/jira/browse/CXF-8446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17312413#comment-17312413
]
Freeman Yue Fang commented on CXF-8446:
---------------------------------------
Hi [~xardasos],
Thanks for bringing up this discussion.
Firstly, as you said, this is a JAXB issue, and better that JAXB should make
this error counter configurable. CXF can't control this.
For the default value of "set-jaxb-validation-event-handler" in CXF, we can't
switch it off, as this is quite important check for other users and this change
can cause backwards compatibility issue. You can switch it off in your
application if this is better for your scenario.
Best Regards
Freeman
> Inconsistent jaxb validation
> ----------------------------
>
> Key: CXF-8446
> URL: https://issues.apache.org/jira/browse/CXF-8446
> Project: CXF
> Issue Type: Improvement
> Components: JAXB Databinding
> Affects Versions: 3.3.9
> Reporter: Tomasz Zorawik
> Priority: Major
>
> I experienced the same issue as described here:
> [https://www.mail-archive.com/[email protected]/msg44090.html]
> The above thread does not mention the reason but it seems that it is caused
> by jaxb issue:
> [https://github.com/javaee/jaxb-v2/issues/1139]
> After around 10 failed validations (there is a global static counter, not
> thread-safe) jaxb validation turns off.
> In my case after a restart of an application (which caused a reset of the
> counter) requests which were processed correctly before the restart suddenly
> started to become rejected. It seems that this is not a CXF bug, but I think
> such behavior can be confusing which is why I decided to report it here. I
> wonder, maybe by default this unreliable validation should be turned
> off{color:#172b4d} (set-jaxb-validation-event-handler = false) {color}in
> future releases of CXF?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
