Bug 786184
Summary: | Remove gwt-log logging mechanism and replace with standard GWT logging | ||
---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | Mike Thompson <mithomps> |
Component: | Core UI | Assignee: | Mike Thompson <mithomps> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 4.2 | CC: | ccrouch, hrupp, mithomps |
Target Milestone: | --- | ||
Target Release: | RHQ 4.3.0 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-09-01 10:18:13 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 735475 | ||
Bug Blocks: | 782579 |
Description
Mike Thompson
2012-01-31 16:53:42 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. 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 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. |