Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [corona-dev] Corona Logging

I think we are all in agreement to use the OSGi logging interfaces.  This will allow us to have a native OSGi approach to create log entries while allowing us to use LogListener to customize output to multiple destinations such as Log4J, native Eclipse logging, etc...
 
Edyta has been assigned the task (https://bugs.eclipse.org/bugs/show_bug.cgi?id=152456) of defining how Corona plug-ins will utilize logging. 

________________________________

From: corona-dev-bounces@xxxxxxxxxxx on behalf of Marcin Okraszewski
Sent: Wed 8/2/2006 3:32 AM
To: Corona development
Subject: Re: [corona-dev] Corona Logging



One more reason for OSGi Logging is that we can still provide a log
listener which would write it to Eclipse log. So the log could be
written to both log4j and Eclipse at the same time. I must say that
"Error log" view is convinient to use.

Marcin


> We discussed logging at our weekly team meeting and thought we would
> use OSGi Logging interfaces wrapped around log4j. This approach should
> allow us to take advantage of any OSGi specific capabilities while
> still supporting a large number of non-OSGi servers.
>
> Edyta will be looking at implementing this design and post any issues.
>
> We still need approval for the Apache log4j.
>
> A few of the reasons we decided on this:
>
> - ALF, Higgins are using log4j
>
> - log4j is can be used by Axis
>
> - log4j is easy to use with web services
>
> - There are log viewers with filtering capability available -
> LogFactor5, Chainsaw
>
> - works with Apache Muse WSDM implementation
>
> - there already exists an OSGi bundle in TPTP for log4j
> org.apache.jakarta_log4j_logging
>
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
_______________________________________________
corona-dev mailing list
corona-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/corona-dev



The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. 

<<winmail.dat>>


Back to the top