Re: Issue with jakarta-stream multipart parser

2016-01-07 Thread Christoph Nenning
> > Please create a jira issue for that. > > I see one was done yesterday along with a fix, also resolving the > related issue when a file field in a form is empty. > > https://issues.apache.org/jira/browse/WW-4583 > That's great! So you can either wait for next release or use a snapshot build

Re: Issue with jakarta-stream multipart parser

2016-01-07 Thread Stephen H
On 07/01/2016 09:42, Christoph Nenning wrote: Please create a jira issue for that. I see one was done yesterday along with a fix, also resolving the related issue when a file field in a form is empty. https://issues.apache.org/jira/browse/WW-4583

Re: Issue with jakarta-stream multipart parser

2016-01-07 Thread Christoph Nenning
> The error message comes from the IllegalArgumentException thrown by > java.io.File.createTempFile() - it doesn't feature in the Struts > distribution at all. Because there's no entry in > struts-messages.properties for > struts.messages.upload.error.IllegalArgumentException it gets added to

Re: Issue with jakarta-stream multipart parser

2016-01-05 Thread Stephen H
https://www.apache.org/dist/struts/2.3.24.1/ is the struts 2.3.4.1 you are working with Martin __ To: user@struts.apache.org From: stephen+li...@jiglu.com Subject: Issue with jakarta-stream multipart parser Date: Tue, 5 Jan 2016 15:58:30 + I&

RE: Issue with jakarta-stream multipart parser

2016-01-05 Thread Martin Gainty
.apache.org/dist/struts/2.3.24.1/ is the struts 2.3.4.1 you are working with Martin __ > To: user@struts.apache.org > From: stephen+li...@jiglu.com > Su

Issue with jakarta-stream multipart parser

2016-01-05 Thread Stephen H
I'm having a problem using the jakarta-stream multipart parser when a filename is used that is just a single character long excluding the suffix. This triggers a check in java.io.File.createTempFile that ensures that a supplied prefix must be at least three characters long: java.lang.IllegalAr