Community
Participate
Working Groups
It seems like each of the BIRT project uses subtly different implementation of logging. As I write code to extend/integrate BIRT, I want my logging to be a natural extension of the BIRT logging that all ready exists (this includes DTP). I know how to introduce my own logging mechanisms (i.e. Log4j, commons.logging, etc.) but I would really like to leverage any logging framework all ready in place for BIRT. I am relatively confident that there is a good way to do this, I just don't know it yet Example documentation that shows logging best practices would be extremely useful.
I have thought about this some more, and have a proposal for an enhancement. It would be very useful, if there were pages within the Window => Preferences => Report Design entitled Logging. Within this page the user could configure one or more login handlers and one or more package loggers. The default implementation would be set up with reasonable attributes for various existing BIRT packages (DTP, Scripting, Core...) and the user could add additional packages for their own classes. I would recommend doing this using the java.util.logging implementation. A use case would be for the user a) To first add/modify the login handlers b) Create new package loggers as needed and then for the package logger set: Level Format pattern or formatter class Configuration file location Handlers
New feature, consider to support in next release.
add plan key word for 2.3/3.0 release planing.
