Mailing-List: contact cxf-issues-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cxf-dev@incubator.apache.org
Message-ID: <508607.1191236510967.JavaMail.jira@brutus>
Date: Mon, 1 Oct 2007 04:01:50 -0700 (PDT)
From: "benson margulies (JIRA)" <jira@apache.org>
To: cxf-issues@incubator.apache.org
Subject: [jira] Commented: (CXF-1083) LogUtils is missing some
 MissingResourceException handling
In-Reply-To: <28749109.1191167991247.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CXF-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531467 ] 

benson margulies commented on CXF-1083:
---------------------------------------

What is needed first and foremost is a systest that turns this on.

Along with a bean to make it easier to do in spring :-)

When I have the trunk and karma I'll do it.


> LogUtils is missing some MissingResourceException handling
> ----------------------------------------------------------
>
>                 Key: CXF-1083
>                 URL: https://issues.apache.org/jira/browse/CXF-1083
>             Project: CXF
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.2
>            Reporter: benson margulies
>            Assignee: Daniel Kulp
>            Priority: Blocker
>
> In LogUtils.createLogger, there is no handling for MissingResourceException when there is a custom logger class.
> The Log4jClass, delegating to the Abstract class, gets just the same collection of missing resource exceptions as the default case. So it blows up.
> The code in createLogger only fails to handle if the name is non-null. If the name is null, it has a try block. Looks to me as if the == null test is backwards.

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