[MAGNOLIA-3859] Default log4j.xml does not log activation in separate file anymore since package name changed Created: 14/Oct/11 Updated: 10/Jan/12 Resolved: 03/Jan/12 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | activation |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.6, 4.5 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Magnolia International | Assignee: | Milan Divilek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||
| Description |
|
The default log4j.xml uses the info.magnolia.cms.exchange category for logging into the separate magnolia-activation.log file, but this package is now only in core; the actual implementations happen in info.magnolia.module.exchangesimple. Since the transactional activation module (EE) uses a different package structure, the log configuration should also be adapted for those - although since this is outside the default bundle, it's arguable whether we should do this in the default log4j file or not. |
| Comments |
| Comment by Magnolia International [ 28/Dec/11 ] |
|
So what is the resolution to the "argument" above ? How do we / did we / decide what goes in the default logging configuration file, despite the fact they might not be part of the default bundle (i.e. transactional activation module classes, which are from an EE module, are referred to in the empty-webapp's log4j.xml file) |