Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Message-ID: <1148656517.1236273116943.JavaMail.jira@brutus>
Date: Thu, 5 Mar 2009 09:11:56 -0800 (PST)
From: "Clement Escoffier (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Subject: [jira] Resolved: (FELIX-966) iPOJO: Better error reporting when
 getPojoObject return null
In-Reply-To: <735754362.1236028976468.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Clement Escoffier resolved FELIX-966.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: iPOJO-1.4.0

Fixed at revision 750499.
When the creation of a pojo object failed, a runtime exception is thrown.

> iPOJO: Better error reporting when getPojoObject return null
> ------------------------------------------------------------
>
>                 Key: FELIX-966
>                 URL: https://issues.apache.org/jira/browse/FELIX-966
>             Project: Felix
>          Issue Type: Improvement
>          Components: iPOJO
>    Affects Versions: iPOJO-1.2.0
>            Reporter: James Kingsbery 
>            Assignee: Clement Escoffier
>             Fix For: iPOJO-1.4.0
>
>
> When InstanceManager's getPojoObject returns null (which happens when createObject returns null), it is really hard to understand why this is the case, since the Exception/Error is hidden from the upper layers behind the null return. I think it would be better if it returned an unchecked exception containing as the cause the underlying Exception/Error - getting null back is not a useful value.

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