On 2010/05/04 21:59:45, unnurg wrote:
OK - it turns out that delegating to another LogManager for the server code is not working correctly. Specifically, there's something in the configurations that isn't getting passed on to the serverLogManager. I spent about 3 hours trying to figure this out and then figured that it was time to go the simple route first and come back and do the harder stuff in a follow up issue. So - I'm sending a patch to this issue now that gets rid of all the attempting to read out the old logging.manager property and just warns the user that this is not supported. Then for server side code, I'm back to just delegating to super (which seems to work fine). There's a TODO(unnurg) to add support for the old log manager property stuff. http://gwt-code-reviews.appspot.com/437801/show -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
