You are viewing a plain text version of this content. The canonical link for it is here.
Posted to adffaces-issues@incubator.apache.org by "Matthias Weßendorf (JIRA)" <ad...@incubator.apache.org> on 2007/03/16 08:37:15 UTC

[jira] Updated: (ADFFACES-21) Mis-ordering of statics un UIComponentUINode defeats logging/stacktraces

     [ https://issues.apache.org/jira/browse/ADFFACES-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthias Weßendorf updated ADFFACES-21:
---------------------------------------

        Fix Version/s: 1.0.0-incubating-core
    Affects Version/s: 1.0.0-incubating-core

> Mis-ordering of statics un UIComponentUINode defeats logging/stacktraces
> ------------------------------------------------------------------------
>
>                 Key: ADFFACES-21
>                 URL: https://issues.apache.org/jira/browse/ADFFACES-21
>             Project: MyFaces ADF-Faces
>          Issue Type: Bug
>    Affects Versions: 1.0.0-incubating-core
>            Reporter: Ryan Williams
>         Assigned To: Matthias Weßendorf
>            Priority: Minor
>             Fix For: 1.0.0-incubating-core
>
>         Attachments: static_ordering.patch
>
>
> In UIComponentUINode, the method _loadRenderertypeToLocalnameMap() uses a static AdfLogger instance when it encounters certain failure conditions (such as a malformatted .properties file).  Unfortunately, due to the ordering of the statics, the logger isn't instantiated yet at the time of the call.   So, instead of safely logging the message and possibly continuing, the application instead crashes with some of the weirdest errors known to man.
> The solution is simple: move the logger declaration/instantiation up above the method that uses it.  I'll attach a patch that does this.

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