Eugen, There is a special method which is intentionally deprecated (i.e. designed for internal use and subject to change): Log.diagnostic()
Does that help? Fred On Mon, Jan 24, 2011 at 3:01 AM, ep <[email protected]> wrote: > hi Fred, > > do you think it makes sence to enable tagging of LogRecords? I'd have > abused category member but unfortunately thereis no getter ;) Or maybe > the LogRecord could store the source logger in some transient field. > The reason behind is I want to avoid bounces in some of my loggers > (logrecords being logged from that logger shall not be processed by > origin logger). Or do you have another idea how to prevent bounces, > yet be able to issue logs from within loggers chain? > > I noticed the HashMap which I could use for such a tagging, but that > field is serializable, so I'll have to clear it anytime I put the > LogRecord on RPC.... :( My logger inhertits from your RemoteLogger but > implements custom RPC mechanics. > > cheers, > Eugen > > -- > You received this message because you are subscribed to the Google Groups > "gwt-log" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<gwt-log%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/gwt-log?hl=en. > > -- Fred Sauer Developer Advocate Google Inc. 1600 Amphitheatre Parkway Mountain View, CA 94043 [email protected] -- You received this message because you are subscribed to the Google Groups "gwt-log" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/gwt-log?hl=en.
