Mailing-List: contact user-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Users Mailing List" <user@struts.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <47F14F4C.2070108@cyberspaceroad.com>
Date: Mon, 31 Mar 2008 21:53:32 +0100
From: Adam Hardy <ahardy.struts@cyberspaceroad.com>
User-Agent: Icedove 1.5.0.14pre (X11/20080305)
MIME-Version: 1.0
To: Struts Users Mailing List <user@struts.apache.org>
Subject: Re: testing file uploads
References: <77380.66032.qm@web56701.mail.re3.yahoo.com>
In-Reply-To: <77380.66032.qm@web56701.mail.re3.yahoo.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Dave Newton on 31/03/08 18:42, wrote:
> --- Adam Hardy <ahardy.struts@cyberspaceroad.com> wrote:
>> I need to test an action that is getting uploaded files and piping them
>> straight into Strings. I don't want to save actual files on server, so I'll
> 
>> get the multipart request wrapper directly.
> 
> What, specifically, are you trying to test?
> 
> I ask because I've never had any particular reason to test file uploads
> inside the container, because the container itself should have already tested
> that and verified its operations. Everything else I've ever done with files
> has been testable outside the container.

The action has to get strings out of the request, work out which file they are 
from and call the appropriate managers, with the corresponding string as a 
request. There's logic in the action that basically has nothing to do with how 
the container handles it (I hope).


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org