Eclipse Community Forums: Eclipse 4 » read log programmatically

Help

Home

Home » Eclipse Projects » Eclipse 4 » read log programmatically

Show: Today's Messages :: Show Polls :: Message Navigator

read log programmatically [message #1067009]

Fri, 05 July 2013 12:14

Jan Weidauer

Messages: 49
Registered: July 2009

Member

Hi there,

I am looking for a way to read the log in my RCP programmatically.
I tried this
ServiceReference<LogReaderService> serviceReference =
context.getServiceReference(LogReaderService.class);
LogReaderService service = context.getService(serviceReference);
Enumeration log2 = service.getLog();
Object object;
while(log2.hasMoreElements()) {
object = log2.nextElement();
System.out.println(object);
}
but the Enumeration contains just an empty collection. How do I read the
log in e4 without compatibility layer?

Regards,

Jan

Report message to a moderator

Re: read log programmatically [message #1067023 is a reply to message #1067009]

Fri, 05 July 2013 13:17

Christoph Keimel

Messages: 482
Registered: December 2010
Location: Germany

Senior Member

Hi Jan

we register our own LoggerProvider, so that the Platform uses the same Logging-Framework than our application. In our case this is SLF4J.

@Override
public void start(BundleContext bundleContext) throws Exception {
	// Use SLF4J as LoggerProvider for e4
	ILoggerProvider service = new ILoggerProvider() {
		@Override
		public org.eclipse.e4.core.services.log.Logger getClassLogger(Class<?> clazz) {
			return new Slf4jLoggerWrapper(LoggerFactory.getLogger(clazz));
		}
	};
	bundleContext.registerService(ILoggerProvider.class.getName(), service, null);
}

Hope this helps!
Christoph

Report message to a moderator

Re: read log programmatically [message #1067137 is a reply to message #1067023]

Sat, 06 July 2013 08:44

Frank Schaare

Messages: 8
Registered: July 2009

Junior Member

Hi,
Christoph Keimel wrote on Fri, 05 July 2013 09:17

we register our own LoggerProvider, so that the Platform uses the same Logging-Framework than our application. In our case this is SLF4J.

nice Approach.
You may also ask yourself: Do i need logging ?

EventBroker can be used for messaging and gives you high flexibility passing your own Objects to the bus:

broker.send(Topics.LOGGING, "message");

This solves the problem with yet missing ConsoleView too; you can now easily create a Console Part holding a message Table and consume logging information like:

@Inject
@Optional
public void handleEvent(@UIEventTopic(Topics.LOGGING) String msg){}

You can pass complex Error Objects holding IStatus & Exceptions to the broker.
You may easily implement a ConsoleHandler which writes all your stuff to the console.
So again: who needs logging in an e4 Application ?

Report message to a moderator

Previous Topic:	E4 demos exist?
Next Topic:	Error on Startup - Could not run processor

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 22:12:42 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter