[corona-dev] Logging in Corona

["Everitt, Glenn" <Glenn.Everitt@xxxxxxxxxxxxx>]

We have a several logging options:

           

-          workbench

-          equinox

-          platform

-          log4j

-          common base events

 

 

Since we have client side components and server side components as well as web service components it seems a compromise may be required.  I would like log formats to be compatible so that can be combined (in time sequence) for analysis of problems that span client and server components.  It would also be nice to take advantage of the native logging support in eclipse workbench and equinox since viewer are already available in eclipse IDE for them.  The log4j option is appealing since we have web services that will initially be using the Apache Axis and log4j is available and stand alone log4j viewer are available.  TPTP project defined common base events providing a common log record for log analyzers use.

 

The logging issue also touches issues such a trace, debug logging capabilities which I have found invaluable in client server environments.  The ability to dynamically enable trace/debug type of logging can eliminate weeks of trying get the information for problem determination.

 

Finally, to completely inflame passions on this topic, should we tie our exception handling into the logging framework.  How can we handle logging from non-Eclipse components that we use such as Apache Muse, Apache Axis which has several of their own logging packages?

 

Please post your thoughts on the most appropriate logging mechanism for the Corona environments.

 

Glenn Everitt

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.