Return-Path: Delivered-To: apmail-commons-user-archive@www.apache.org Received: (qmail 42273 invoked from network); 15 Mar 2011 23:50:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Mar 2011 23:50:37 -0000 Received: (qmail 55672 invoked by uid 500); 15 Mar 2011 23:50:36 -0000 Delivered-To: apmail-commons-user-archive@commons.apache.org Received: (qmail 55605 invoked by uid 500); 15 Mar 2011 23:50:36 -0000 Mailing-List: contact user-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Users List" Delivered-To: mailing list user@commons.apache.org Received: (qmail 55597 invoked by uid 99); 15 Mar 2011 23:50:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Mar 2011 23:50:36 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of sebbaz@gmail.com designates 209.85.216.171 as permitted sender) Received: from [209.85.216.171] (HELO mail-qy0-f171.google.com) (209.85.216.171) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Mar 2011 23:50:30 +0000 Received: by qyj19 with SMTP id 19so2541591qyj.9 for ; Tue, 15 Mar 2011 16:50:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=lPuFdHmhetUX4NiYjjb2xQGZdZ84cIYJXiS/b95jG88=; b=JRRoI9DPmxt35swv9/rzK2QtxpxciLHGPU5aIjCS8uKRUBmgcngerC+uQr30B+bbe0 DCSvp4qFX35Jc14L8ENXMz1Uq312TI2DrFDeSrnH7Te8gHZkb/9qIiXLHovMQladOcv1 Tc+cbIsggT49MCfi9sXTWLeaKsNYsyoxdig5s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=oM5Hl78oJPc8DP/5IpgvD5jCRfMFkeOeMGGidR3W7dX2I0vfZOMtY9AaIGo0oMENuU po13xYcQBDfpL9CBHBXAfjm74YwUyGNYnXEo8gvUuoPABVfJyU9WWwYsvw8+vVTSHmgg nDbQkz713UNTWljke9imya85g3E4PwrYitLRo= MIME-Version: 1.0 Received: by 10.229.225.199 with SMTP id it7mr86803qcb.188.1300233009155; Tue, 15 Mar 2011 16:50:09 -0700 (PDT) Received: by 10.229.24.69 with HTTP; Tue, 15 Mar 2011 16:50:09 -0700 (PDT) In-Reply-To: <61664300480FCF4EAC0C1A5C431A6FCC2BFCD5BB@atl-exch2.DHLGLOBALMAIL.CORP> References: <61664300480FCF4EAC0C1A5C431A6FCC2BFCD5BB@atl-exch2.DHLGLOBALMAIL.CORP> Date: Tue, 15 Mar 2011 23:50:09 +0000 Message-ID: Subject: Re: [NET] ParserInitializationException root cause From: sebb To: Commons Users List Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On 15 March 2011 23:40, Daniel Gredler wrote: > Hi all, > > > > I have a question about ParserInitializationException; it appears to > have its own "rootCause" instance variable, rather than using > RuntimeException's constructors which allow a cause to be specified > (ParserInitializationException extends RuntimeException). So for example > on line 53 of the class [1], I would expect to see a simple invocation > to "super(message, rootCause)". > > > > The reason this has come up is that we're logging these exceptions using > log4j, but because ParserInitializationException doesn't use the > standard JDK exception chaining, we don't get visibility into the root > issue. Does anyone know why this exception was built this way? Commons NET 1.4.1 targets Java 1.3+, and RuntimeException only added chaining in 1.4. Commons NET 2.x targets 1.5+, but was derived from the 1.x codeline. > Would anyone else consider this a bug? Feel free to raise JIRA issue to get this changed. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@commons.apache.org For additional commands, e-mail: user-help@commons.apache.org