Bug 786184 - Remove gwt-log logging mechanism and replace with standard GWT logging
Summary: Remove gwt-log logging mechanism and replace with standard GWT logging
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.2
Hardware: All
OS: All
low
low
Target Milestone: ---
: RHQ 4.3.0
Assignee: Mike Thompson
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On: rhq-uxd
Blocks: jon310-sprint11, rhq44-sprint11
TreeView+ depends on / blocked
 
Reported: 2012-01-31 16:53 UTC by Mike Thompson
Modified: 2013-09-01 10:18 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-01 10:18:13 UTC
Embargoed:


Attachments (Terms of Use)

Description Mike Thompson 2012-01-31 16:53:42 UTC
GWT 2.x has rolled in much of the logging functionality into the core framework. Prior to GWT 2.x there was no other logging framework, however, the later versions of GWT have incorporated almost all the functionality of gwt-log.



gwt-log: http://code.google.com/p/gwt-log/
GWT Logging: http://code.google.com/webtoolkit/doc/latest/DevGuideLogging.html

Comment 1 Mike Thompson 2012-02-03 16:09:29 UTC
I have fixed the api compatiblity issues by adding an adapter (Log) that makes the GWT logging (jdk logging) appear api compatible with  gwt-log (log4j style) logging.

This is one approach, I'm sure there are others. Or you could just use native jdk  logging outright.

1) instantiating a logger
Logger logger = Logger.getInstance(""); // put in whatever category

2) log your message with new and different levels
logger.fine("my log message");



A new option with jdk logging is the ability to CONFIG loggging, which can be useful in itself.

Comment 2 Mike Thompson 2012-02-20 15:26:13 UTC
Although, you could look at the javascript console and server log files to verify that we are still getting output in both places.

Commit: 1bcc7b0

Comment 3 Heiko W. Rupp 2013-09-01 10:18:13 UTC
Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.


Note You need to log in before you can comment on or make changes to this bug.