| Summary: | JavaUtilLoggerImpl creates LogRecord without logger name | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Aaron Digulla <digulla> | ||||
| Component: | BIRT | Assignee: | Birt-Chart-inbox <Birt-Chart-inbox> | ||||
| Status: | NEW --- | QA Contact: | weiming tang <weiming.tang> | ||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | bluesoldier, weiming.tang | ||||
| Version: | 3.7.0 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Aaron Digulla
(In reply to comment #0) > The code in JavaUtilLoggerImpl creates LogRecord without setting the source > logger name which causes problems in some logging frameworks. > > The attached patch merges common code and makes sure LogRecord is completely > initialized. Can this problem be reproducable in the latest build? Could you add more information about this problem? Created attachment 205807 [details]
Patch which fixes the issue
Bugzilla sometimes swallows attachments made when a bug is created. Here is the patch.
|