[
https://issues.apache.org/jira/browse/XMLBEANS-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17325042#comment-17325042
]
Travis Schneeberger commented on XMLBEANS-564:
----------------------------------------------
Noisy is probably the wrong word. We have used XMLbeans for a while and not
just legacy applications. Having said that, we aren't familiar with all the
configuration options available. When we initially tried to upgrade we noticed
a new stacktrace on application startup. Since this was new and came from a
class that indicated a configuration check we were not comfortable continuing
with the upgrade without further analysis.
So, maybe suppressing the stacktrace by default or clarifying the logged
message would be helpful in making it look less like an important error. This
is subjective and just a suggestion obviously.
> SAXHelper creates noisy logging with stacktraces
> ------------------------------------------------
>
> Key: XMLBEANS-564
> URL: https://issues.apache.org/jira/browse/XMLBEANS-564
> Project: XMLBeans
> Issue Type: Improvement
> Affects Versions: Version 5.0.0
> Reporter: Travis Schneeberger
> Priority: Minor
>
> Upgrading to xmlbeans 5 creates new noisy logging when xerces is not
> available. We aren't sure if this indicates a runtime library problem or is
> unnecessarily noisy but regardless this type of logging did not occur in
> previous versions. The code in question is: SAXHelper.
> trySetXercesSecurityManager(). Please advise. Thank you.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
