Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Date: Wed, 27 Nov 2013 16:01:35 +0000 (UTC)
From: "Guillaume Nodet (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Message-ID: <JIRA.12681595.1385564757901.39146.1385568095221@arcas>
In-Reply-To: <JIRA.12681595.1385564757901@arcas>
References: <JIRA.12681595.1385564757901@arcas>
Subject: [jira] [Resolved] (GERONIMO-6509) XMLStreamException not calling
 "super(th)" in constructors
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Guillaume Nodet resolved GERONIMO-6509.
---------------------------------------

    Resolution: Fixed

> XMLStreamException not calling "super(th)" in constructors
> ----------------------------------------------------------
>
>                 Key: GERONIMO-6509
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6509
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: specs
>            Reporter: Daniel Kulp
>            Assignee: Guillaume Nodet
>
> The XMLStreamException in spec stax-api 1.2 is not calling the super(th) or super(msg, th) for the constructors that take a throwable.   There are two problems this causes:
> 1) The "cause" is never set so the exception.getCause() always returns null and potentially important information in the cause is discarded.
> 2) For the super(th) one,  no message is set at all.    Thus, all information that could be useful is lost unless I specifically cast the exception to an XMLStreamException and call the getNestedException().   Any generic exception handling mechanism would not be able to provide a useful error message.


--
This message was sent by Atlassian JIRA
(v6.1#6144)