[
https://issues.jboss.org/browse/JBWS-3997?page=com.atlassian.jira.plugin....
]
Alessio Soldano commented on JBWS-3997:
---------------------------------------
Some comments:
* I don't see much value in modifying the WSProvide / WSConsume classes, those are
command line tools. And in any case the stacktrace prints there are actually needed
(they're not there only because of lazy coding ;) )
* I'm fine with changing the CopyJob and Base64 classes
jbossws-common - usage of Exception.printStackTrace() instead of
logging feature
--------------------------------------------------------------------------------
Key: JBWS-3997
URL:
https://issues.jboss.org/browse/JBWS-3997
Project: JBoss Web Services
Issue Type: Enhancement
Reporter: Ingo Weiss
Assignee: Ingo Weiss
Priority: Minor
Original Estimate: 2 hours
Remaining Estimate: 2 hours
4x
https://github.com/jbossws/jbossws-common/blob/master/src/main/java/org/j...
4x
https://github.com/jbossws/jbossws-common/blob/master/src/main/java/org/j...
1x
https://github.com/jbossws/jbossws-common-tools/blob/master/src/main/java...
1x
https://github.com/jbossws/jbossws-common-tools/blob/master/src/main/java...
In both there are checks on Log4JUtil.isLog4jConfigurationAvailable() in previous part of
the code
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)