Return-Path: Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list commons-user@jakarta.apache.org Received: (qmail 72638 invoked from network); 11 Jul 2003 17:39:44 -0000 Received: from mail.6degrees.com (64.51.116.5) by daedalus.apache.org with SMTP; 11 Jul 2003 17:39:44 -0000 Message-id: Date: Fri, 11 Jul 2003 13:40:43 -0400 Subject: Re: fileUpload NullPointerException To: "Jakarta Commons Users List" From: "Daryl Stultz" References: <1057925436.587.47.camel@phoenix> <3F0EEA8B.5050708@printtime.com> In-Reply-To: <3F0EEA8B.5050708@printtime.com> MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N "Jakarta Commons Users List" writes: > o There is a file upload field that the user is not selecting, and as >such it is returning a blank or null value to FileUpload. This would >usually throw a FileUpload Exception instead though. So I would focus on >the first two. I have a page that has three upload fields. You can select a file for only one (or none at all) and it does not throw an error. Given that the upload field may be an optional feature for the user, it seems that throwing an exception is not a great design. Am I missing something here? Is it the parseRequest method that will throw the exception or something else? Thanks. Daryl Stultz _____________________________________ 6 Degrees Software and Consulting, Inc. http://www.6degrees.com mailto:daryl@6degrees.com