Hi, Thanks for your reply Brian. It clarifies quite a few things.
I have implemented the ILoggerProvider with a slf4j wrapper. Regarding the appender, can you elaborate how to access the FrameworkLog instance. I am implementing the appender as a fragment for ch.qos.logback.classic bundle. Is there something else that I am missing? Regards, Ashwin On Sat, Jun 7, 2014 at 9:30 PM, <[email protected]> wrote: > Send e4-dev mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > https://dev.eclipse.org/mailman/listinfo/e4-dev > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of e4-dev digest..." > > > Today's Topics: > > 1. Re: Eclipse E4 Logger based Slf4j binding (Brian de Alwis) > 2. 0.16 Build: I20140606-2200 submission ([email protected]) > 3. 0.16 Build: I20140606-2200 Failed ([email protected]) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 6 Jun 2014 19:45:30 -0400 > From: Brian de Alwis <[email protected]> > To: E4 Project developer mailing list <[email protected]> > Subject: Re: [e4-dev] Eclipse E4 Logger based Slf4j binding > Message-ID: <[email protected]> > Content-Type: text/plain; charset=windows-1252 > > Hi Ashwin. > > If I understand correctly, you?re seeking to write an SLF4j backend that > will shunt all messages from the different SLF4j facades through an > appropriate E4 logger? > > The E4 Logger is itself a facade. There?s an ILoggerProvider which is > intended to act like the SLF4j LoggerFactory: provide a logger for a > particular class. The app can provide a different ILoggerProvider than the > DefaultLoggerProvider that is installed by default, that just logs using > the Equinox/OSGi logger. > > My 2?: I think you should reconsider your approach. Instead of shunting > to the E4 Logger, use SLF4j (SLF4j?s markers and MDC are very powerful) and > use one of the existing SLF4j backends. Provide your own ILoggerProvider > that just wraps the SLF4j Logger. With Logback or Log4j, you can write an > appender that can send log messages back to the Equinox FrameworkLog if > it?s important to have messages go through the Eclipse logging mechanism > (i.e., to show up in the Error Log view). > > Brian. > > On 6-Jun-2014, at 6:19 AM, Ashwin Jha <[email protected]> wrote: > > > Hi, > > > > I am implementing a Eclipse E4 Logger based binding for SLF4J. > > I wanted to know how to access the Logger instance as my > > implementation will be a fragment hosted by the org.slf4j.api bundle. > > > > > > Thanks, > > Ashwin > > _______________________________________________ > > e4-dev mailing list > > [email protected] > > https://dev.eclipse.org/mailman/listinfo/e4-dev > > > > ------------------------------ > > Message: 2 > Date: Fri, 06 Jun 2014 22:00:51 -0400 > From: [email protected] > To: [email protected] > Subject: [e4-dev] 0.16 Build: I20140606-2200 submission > Message-ID: <[email protected]> > Content-Type: text/plain; charset=us-ascii > > The following projects have changed: > > The build contains commits that mentioned these bugs: > > > ------------------------------ > > Message: 3 > Date: Fri, 06 Jun 2014 22:03:16 -0400 > From: [email protected] > To: [email protected] > Subject: [e4-dev] 0.16 Build: I20140606-2200 Failed > Message-ID: <[email protected]> > Content-Type: text/plain; charset=us-ascii > > Build log: http://build.eclipse.org/eclipse/e4/cbi/log.txt > > > > ------------------------------ > > _______________________________________________ > e4-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/e4-dev > > > End of e4-dev Digest, Vol 68, Issue 7 > ************************************* >
_______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev
