[JBoss JIRA] (JBWS-3997) jbossws-common - usage of Exception.printStackTrace() instead of logging feature - jbossws-issues

Thursday, 23 June 2016

     [
https://issues.jboss.org/browse/JBWS-3997?page=com.atlassian.jira.plugin....
]

Ingo Weiss updated JBWS-3997:
-----------------------------
              Project: JBoss Web Services  (was: JBoss Enterprise Application Platform)
                  Key: JBWS-3997  (was: JBEAP-5106)
           Issue Type: Enhancement  (was: Bug)
             Workflow: classic default workflow  (was: CDW with loose statuses v1)
               Status: Open  (was: New)
          Component/s:     (was: Web Services)
       Target Release:   (was: 7.backlog.GA)
    Affects Version/s:     (was: 7.0.0.GA)

...
 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)

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

[JBoss JIRA] (JBWS-3997) jbossws-common - usage of Exception.printStackTrace() instead of logging feature