[JS2-1099] Portlet application's error logs should be found in its own log file, not in jetspeed's log file.

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.2.1
• Assignee: Woonsan Ko
• Reporter: Woonsan Ko
• Created: 05/Feb/10 16:11
• Updated: 04/Oct/11 21:04
• Resolved: 05/Feb/10 16:20

Description

Currently, if a portlet throws exception, then the exception is logged in the jetspeed log file instead of its own log file.
This is because JetspeedContainerServlet cannot access the application's slf4j logger when available due to classloader boundary.
This problem can be solved if a JetspeedLogger implements delegating to PA's logger if available by reflection.
Also, it would not be a overhead to retrieve PA's logger because it can done only once when the servlet meets an exception.
By the way, the other logs related to initialization/destroying of PA should be logged in jetspeed log file as it has been done.