Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Tue, 31 Jan 2012 12:40:10 +0000 (UTC)
From: =?utf-8?Q?Jean-Baptiste_Onofr=C3=A9_=28Created=29_=28JIRA=29?=
 <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: 
 <1874794542.11388.1328013610766.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (KARAF-1175) Duplicate key exception should be
 handle locally to avoid to affect the whole MBean
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Duplicate key exception should be handle locally to avoid to affect the who=
le MBean
---------------------------------------------------------------------------=
--------

                 Key: KARAF-1175
                 URL: https://issues.apache.org/jira/browse/KARAF-1175
             Project: Karaf
          Issue Type: Bug
          Components: karaf-config, karaf-features
    Affects Versions: 2.2.5, 2.2.4
            Reporter: Jean-Baptiste Onofr=C3=A9
            Assignee: Jean-Baptiste Onofr=C3=A9
             Fix For: 2.2.6, 3.0.0


When a MBean returns a TabularData, we have a loop to populate the TabularD=
ata.

If an exception occurs in an iteration (as a duplicate key exception for in=
stance), we don't populate the tabular data at all.

A try/catch should be defined in the iteration, to avoid to get out the MBe=
an with a null value.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira