You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Scott O'Bryan (JIRA)" <de...@myfaces.apache.org> on 2011/08/19 15:56:27 UTC

[jira] [Commented] (PORTLETBRIDGE-218) Upgrade portlet bridge logging to use java logging

    [ https://issues.apache.org/jira/browse/PORTLETBRIDGE-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087720#comment-13087720 ] 

Scott O'Bryan commented on PORTLETBRIDGE-218:
---------------------------------------------

Instead of re-inventing the wheel, perhaps we should consider using sl4j or commons logging.  Many Apache projects, including many of MyFaces, have moved to sl4j because it's plugable, but commons logging would be acceptable as well.

> Upgrade portlet bridge logging to use java logging
> --------------------------------------------------
>
>                 Key: PORTLETBRIDGE-218
>                 URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-218
>             Project: MyFaces Portlet Bridge
>          Issue Type: Improvement
>          Components: API, Impl
>    Affects Versions: 2.0.0
>            Reporter: Alistair Wilson
>            Assignee: Michael Freedman
>
> The portlet bridge currently has limited logging which uses both the PortletContext.log mechanism controlled by a debug enabled/disabled switch (e.g. GenericFacesPortlet) and the java logging mechanism (e.g.PortletFaceletViewHandler or the samples).
> Using a standard jsf bridge specific java logger would simplify the process of changing log levels for deployed portlet applications and allow more control over logging levels in the bridge code.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira