Return-Path: Delivered-To: apmail-jakarta-commons-user-archive@www.apache.org Received: (qmail 48901 invoked from network); 7 Sep 2004 22:16:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 7 Sep 2004 22:16:56 -0000 Received: (qmail 94140 invoked by uid 500); 7 Sep 2004 22:16:48 -0000 Delivered-To: apmail-jakarta-commons-user-archive@jakarta.apache.org Received: (qmail 94083 invoked by uid 500); 7 Sep 2004 22:16:47 -0000 Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Users List" Reply-To: "Jakarta Commons Users List" Delivered-To: mailing list commons-user@jakarta.apache.org Received: (qmail 94059 invoked by uid 99); 7 Sep 2004 22:16:46 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from [202.135.116.201] (HELO unxcoms01.ecnetwork.co.nz) (202.135.116.201) by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 07 Sep 2004 15:16:45 -0700 Received: from serpent.ecnetwork.co.nz (serpent [202.135.190.10]) by unxcoms01.ecnetwork.co.nz (8.12.8/8.12.8) with ESMTP id i87MGcc1001302 for ; Wed, 8 Sep 2004 10:16:38 +1200 Received: from [202.135.190.30] (unknown [202.135.190.30]) by serpent.ecnetwork.co.nz (Postfix) with ESMTP id 50CFF1035 for ; Wed, 8 Sep 2004 10:18:27 +1200 (NZST) Subject: Re: digester: can SetPropertyRule warn on not found properties? From: Simon Kitching To: Jakarta Commons Users List In-Reply-To: References: <1094163840.9347.34.camel@pcsimon> Content-Type: text/plain Message-Id: <1094595382.22012.17.camel@pcsimon> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 08 Sep 2004 10:16:22 +1200 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Wed, 2004-09-08 at 05:05, Gabriele Carcassi wrote: > Hi Simon and Robert, > > Thanks for the answers. > > I had a look at the source and it seems that in dev an exception is thrown: > http://jakarta.apache.org/commons/beanutils/xref/org/apache/commons/beanutils/BeanUtilsBean.html#1013 > but it doesn't seem to block the Digester processing... anyway, I don't > think I will have problem finding why. > > Once I am done, would you like the patch to be contributed back? If so, is > it ok if it depends on the latest version of beanutil? Yes, a patch for Digester would be great. If it is necessary to patch beanutils, then I can't speak for the beanutils developers (which is mostly Robert) but think that a patch for this would also be happily accepted as long as it doesn't break backward compatibility. Having digester depend on an unreleased beanutils is a problem; it means that the next version of Digester could not be released until the next version of beanutils is released. However (optionally) having errors reported for attributes without matching bean properties is a nice feature, so I'm personally willing to consider this. Maybe there is some reflection trick that can be done so that when digester is run with an older beanutils release this feature is just not available? Regards, Simon --------------------------------------------------------------------- To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-user-help@jakarta.apache.org