-
Bug
-
Resolution: Done
-
Minor
-
7.0.0.GA
-
None
Usage of Exception.printStackTrace() instead of logging feature
- https://github.com/jbossws/jbossws-cxf/blob/master/modules/client/src/main/java/org/jboss/wsf/stack/cxf/client/serviceref/CXFHandlerResolverImpl.java#L331
- https://github.com/jbossws/jbossws-cxf/blob/master/modules/client/src/main/java/org/jboss/wsf/stack/cxf/client/serviceref/CXFHandlerResolverImpl.java#L373
- https://github.com/jbossws/jbossws-cxf/blob/master/modules/addons/transports/udp/src/main/java/org/jboss/wsf/stack/cxf/addons/transports/udp/UDPDestination.java#L113
- https://github.com/jbossws/jbossws-cxf/blob/master/modules/addons/transports/udp/src/main/java/org/jboss/wsf/stack/cxf/addons/transports/udp/UDPDestination.java#L200
Most likely leftovers from initial development.
- is cloned by
-
JBWS-3998 jbossws-cxf - usage of Exception.printStackTrace() instead of logging feature
- Closed
- is incorporated by
-
JBEAP-5271 (7.0.z) Upgrade JBossWS from 5.1.3.SP1 to 5.1.5.Final
- Verified