JDK-6899605 : Eliminate dependency on logging from com.sun.tracing
  • Type: Enhancement
  • Component: core-svc
  • Sub-Component: tools
  • Affected Version: 7
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2009-11-10
  • Updated: 2010-08-06
  • Resolved: 2009-11-18
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 7
7Resolved
Related Reports
Duplicate :  
JDK-6902678 - com.sun.tracing.ProviderFactory.createProvider doesn't throw IllegalArgumentException
Relates :  
JDK-6882376 - Add internal support for JRE implementation to eliminate the dependency on logging
Description
The following com.sun.tracing and sun.tracing classes should be changed to use sun.util.logging.PlatformLogger that deals with the case when the logging module doesn't exist:

com.sun.tracing.ProviderFactory          -> java.util.logging.Logger (logging)
sun.tracing.MultiplexProviderFactory     -> java.util.logging.Logger (logging)
sun.tracing.NullProviderFactory          -> java.util.logging.Logger (logging)
sun.tracing.PrintStreamProviderFactory   -> java.util.logging.Logger (logging)
sun.tracing.dtrace.DTraceProviderFactory -> java.util.logging.Logger (logging)
Comments
EVALUATION Close this as a dup of 6902678. When 6902678 is fixed, the log messages are no longer emitted and thus the dependency on logging no longer exist.
18-11-2009
EVALUATION Looks like the log messages are not really needed. The catch clauses attempt to handle permission check where those calls should be wrapped with doPrivilege.
10-11-2009