Ok. I see. I managed to catch the file with a custom component and save it in db.
Has anyone noticed, that if you change the location of upload-dir from web.xml, the files get stuck on that dir? It seems that Cocoon cannot delete the files if it's not the default location. -Tuomo On Tue, 20 Apr 2004, Geoff Howard wrote: > Steve Schwarz wrote: > > > Tuomo > > I believe the behavior changed in 2.1 so that that is no longer true: > > http://wiki.cocoondev.org/Wiki.jsp?page=FileUploadsWithCocoon2.1 > > Steve > > Exactly - and the general security weakness of the old system (unlimited uploads > to any url handled by any cocoon server with uploads enabled) was deemed to be > serious enough to warrant such an incompatible change. > > Geoff > > >> But if autosave-uploads=true, the the file should be saved in the > >> upload-dir permanently, right? > >> > >> -Tuomo > >> > >> On Tue, 20 Apr 2004, Steve Schwarz wrote: > >> > >> > Hi Tuomo > >> > IIRC the file will only exist for the duration of the pipeline > >> invoked by > >> > the form action. So you need to process it within that pipeline as > >> cocoon > >> > deletes it right afterwards. > >> > HTH, > >> > Steve > >> > > >> > >Hi, > >> > > > >> > >We're having some serious problems with Cocoon upload mechanism. > >> Nothing > >> > >ends up in the upload-dir. The form enctype is set to > >> multipart/form-data, > >> > >enable-uploads=true and autosave-uploads=true in web.xml. > >> > > > >> > >What could be the problem? > >> > > > >> > >Running Cocoon 2.1.4 on Tomcat 4.1.24. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
