Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 46974 invoked by uid 500); 11 Jun 2001 16:59:34 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 46957 invoked from network); 11 Jun 2001 16:59:33 -0000 Date: Mon, 11 Jun 2001 12:59:06 -0400 (EDT) From: Donald Ball X-X-Sender: To: cod Subject: Re: [C2] maybeupload In-Reply-To: <20010611175414.18e9e2a5.steffen@smb-tec.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N On Mon, 11 Jun 2001, Steffen Stundzig wrote: > Hi, > > I try to upload a file in my web app into my EJBContainer. But the > MaybeUploadRequestWrapper in cocoon saves it in the filesystem. How can I > customize the maybeupload thing to do what I wish, what it should do? :-) > > I haven't found any methods to access my uploaded file later. Nor could I > disable the MaybeuploadRequestWrapper from an config file, to do the > upload stuff itself. if you call request.get() with the name of your file parameter as an argument, you should get a string with the path to the file where it's stored on the server's filesystem. i've got an outstanding patch that disables the save-to-filesystem option and gives you an InputStream instead. as soon as i've tracked down some (maybe) maybeupload problems (or maybe they're my own) i'll post the patch. - donald --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org