tree 97bed4b5e9ff96eb0d5c094853a90571bef51ef1
parent 7b8f95b682a912ae730df984ee58c1367929c9dd
author baker@google.com <baker@google.com@8db76d5a-ed1c-0410-87a9-c151d255dfc7> 1322517741 +0000
committer baker@google.com <baker@google.com@8db76d5a-ed1c-0410-87a9-c151d255dfc7> 1322517741 +0000

Fix GWT emulated Logger behavior to match java.util.logging.Logger
specification.  This will also make production logging behavior match
devmode behavior since devmode behavior comes from the JRE implementation.

1. getHandlers() should return an empty array rather then null.
2. getLevel() should return null if the Logger has no level explicitly set
(i.e. if it should be inheriting its level from the first ancestor with an
explicity set level).
3. A logging call which passes the logger's level check should be published to
ancestor loggers' handlers recursively up the tree, irrespective of the
log levels of the ancestor loggers.  This process is only stopped by a false
getUseParentHandlers().

Review at http://gwt-code-reviews.appspot.com/1602804

Review by: unnurg@google.com

git-svn-id: https://google-web-toolkit.googlecode.com/svn/trunk@10766 8db76d5a-ed1c-0410-87a9-c151d255dfc7