You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "Woonsan Ko (JIRA)" <je...@portals.apache.org> on 2010/02/05 17:13:28 UTC

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

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

                 Key: JS2-1099
                 URL: https://issues.apache.org/jira/browse/JS2-1099
             Project: Jetspeed 2
          Issue Type: Improvement
            Reporter: Woonsan Ko
            Assignee: Woonsan Ko
             Fix For: 2.2.1


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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org

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

Posted by "Woonsan Ko (JIRA)" <je...@portals.apache.org>.
     [ https://issues.apache.org/jira/browse/JS2-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Woonsan Ko resolved JS2-1099.
-----------------------------

    Resolution: Fixed

> Portlet application's error logs should be found in its own log file, not in jetspeed's log file.
> -------------------------------------------------------------------------------------------------
>
>                 Key: JS2-1099
>                 URL: https://issues.apache.org/jira/browse/JS2-1099
>             Project: Jetspeed 2
>          Issue Type: Improvement
>            Reporter: Woonsan Ko
>            Assignee: Woonsan Ko
>             Fix For: 2.2.1
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org