On Mon, Sep 15, 2003 at 03:29:25AM +0000, Steve Schwarz wrote:
Everything Steve says below is good advice - just offering more detail to dispel some of the magic.
A couple ideas that might help:
Instead of editing the web.xml I'm pretty sure I edited the build.properties (?) by copying it to local.build.properties and flipped a property for file uploads (it's in the file comments) and ran build. Don't know if this setting invokes more magic than you are doing manually...but I seem to recall it creating dirs/etc too (when I moved from 2.0.4 my file uploads were working until I took this step).
These are functionally equivalent. It's one more moving part for now though, so I'd still just modify web.xml by hand (although make sure you've got the one in build/webapp).
But, while we're on the subject, the [local.]build.properties config.enable-uploads setting just modifies web.xml with an xpath statement. It's held in src/confpatch and in this case is called enable-uploads.xweb (see http://wiki.cocoondev.org/Wiki.jsp?page=XPatchTaskUsage at the wiki). Using it has the benefit that if you need to rebuild cocoon for some reason (upgrading to more recent cvs for example) your web.xml setting isn't lost. You don't have to completely rebuild because the custom-conf target can stand alone. You don't need any of this for now but keep it in the back of your head.
I'd use System.out.println() for now to see which of your cases in your action are hit...instead of fighting the logging issue.
good advice.
I also seem to recall an email that in 2.1 files are deleted after the upload unless your action/pipeline copies them/processes them (but I could be all wet about this!!!). So if I'm right the file won't be there when you look for it after you pipleline is executed. You could setup a script to stat the upload-dir in a loop to verify it really shows up...
You are exactly right as I mentioned eventually on the thread (may have been missed). I had completely forgotten about this change until now.
Don't know if I'm helping much here...
You were spot on. Thanks.
You are helping a great deal. I haven't had a minute to give it one last try, but, thanks to you and Geoff, I think I'm very close to getting it to work. As with most programming problems, you have to understand *what* the problem is, and I think I'm starting to get a handle on how this system works.
I'm going to try to write up the whole thing for people who are neither as knowledgable as you *or* Geoff :)
That would be a great contribution. It's been sorely needed and I just haven't been able to get myself to it.
Geoff
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
