Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <003901c4ac97$58f336f0$6600a8c0@katabatic>
From: "Adam Pelletier" <adamp@moebius-solutions.com>
To: <commons-user@jakarta.apache.org>
Subject: FileUpload Parameter Handling
Date: Thu, 7 Oct 2004 10:59:10 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0036_01C4AC5C.AC7C9130"

------=_NextPart_000_0036_01C4AC5C.AC7C9130
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I'm using commons-fileupload-1.0.jar.

I'm trying to upload a file using enctype=3D"multipart/form-data".

However, I'm also passing a hidden form input element with an ID stuck =
in it.  This ID is critical for the state of the servlet.  Oddly, when I =
use the enctype=3D"multipart/form-data", my HttpServletRequest no longer =
seems to contain the parameters usually accessible by =
req.getParameter("ID");.  In the debugger I see that the parameter =
hashtable is empty.  As a test I remove enctype=3D"multipart/form-data" =
from the form.  The parameters then show up properly in the parameter =
map, but now the file is not accessible. =20

Is there a way to utilize both the file uploading capability and still =
have access to the parameter list as it comes in as a =
HttpServletRequest?

Thanks in advance.
Adam
------=_NextPart_000_0036_01C4AC5C.AC7C9130--