Hippo is an add-on for Cocoon. The code in the previous post should work whether added to Hippo or a different Cocoon application. The code is indifferent to whether the Part is a PartOnDisk or a PartInMemory (and fails if the Part is a RejectedPart.) Only the first code to receive the upload should touch it, usually storing it for later use. You should not touch the upload in the request if Hippo has already handled it. Check (and maybe override) the pipeline handling the upload request.
Are you running more than one instance of Cocoon? Why? (Many good reasons exist: politics, performance -- just checking that you have one.) solprovider On 3/5/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > 2. Always mention the version of any software. > We are using version 2.1.11 of cocoon, with a few adjustments of Hippo. (I > don't know exact what they changed.) > > > 3. About your first question, ... Let me know if the remaining work is > not obvious. > > As I just mentioned, we are using some modules from Hippo. I guess we have > to dive deep in their code as they are used to deploy on Jetty, not on > JBoss. I guess JBoss writes their multipart in memory, as I could not find > the file anywhere. > > Thanks for your answer, > Nick Stolwijk --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
