-
Bug
-
Resolution: Done
-
Minor
-
7.0.0.GA
-
None
4x https://github.com/jbossws/jbossws-common/blob/master/src/main/java/org/jboss/ws/common/concurrent/CopyJob.java
4x https://github.com/jbossws/jbossws-common/blob/master/src/main/java/org/jboss/ws/common/utils/Base64.java
1x https://github.com/jbossws/jbossws-common-tools/blob/master/src/main/java/org/jboss/ws/tools/cmd/WSProvide.java#L220
1x https://github.com/jbossws/jbossws-common-tools/blob/master/src/main/java/org/jboss/ws/tools/cmd/WSConsume.java#L301
In both there are checks on Log4JUtil.isLog4jConfigurationAvailable() in previous part of the code
- incorporates
-
JBWS-3997 jbossws-common - usage of Exception.printStackTrace() instead of logging feature
-
- Resolved
-
- is incorporated by
-
JBEAP-5272 (7.1.0) Upgrade JBossWS from 5.1.4.Final to 5.1.5.Final
-
- Verified
-
