far as I know, there will not be a way to automatically handle this because
cocoon's uploads are using java.io.File to automatically save files and I
don't think this will work saving to a webdav folder, which as I understand it
is not a folder at all, but a pointer to a url using the http protocol. If your
particular server and webdav implementation happen to support it though you'll be
in luck but it would be as easy as specifying whatever file path in web.xml you use
for the local webdav "folder" on the server.
If that doesn't work as I suspect, you'll need to write an action to get the FilePart out of the request, call getInputStream and send that input stream over http to the webdav location.
See: http://wiki.cocoondev.org/Wiki.jsp?page=FileUploadWithAction and http://wiki.cocoondev.org/Wiki.jsp?page=FileUploadsWithCocoon
for more information on the process up to and including getting the input stream.
You may also get info from WebServiceProxyGenerator and/or HTTPProxyGenerator
Beyond that though, I'll not be much help. You may want to repost a new question focused on how to send input stream to a webdav repository on another server from within an action.
Geoff Howard
At 09:24 AM 4/2/2003, you wrote:
The end user produce a pdf file and use cocoon (via upload.xsp) to publish it :
upload.xsp provides the end user to select a pdf file and upload it to the server. I just want the server to store this file not on the server HD, but in a webdav directory on an other server. I don't know how to specifying this in web.xml
I hope it's most clear because i can't take you any coffee.
Thanks
Geoff Howard a écrit :
>
> I'm sorry - I must need more coffee. It's still not clear to me. Here's
> my best guess:
>
> You want to upload to upload.xsp, but select a file not from your hard drive
> but from a local shortcut to a webdav directory?
>
> I don't think windows/IE will let you do that. In my experience with
> webdav (not extensive) I've had to save the file locally first, and then
> upload it. This is beyond cocoon's control, though. The issue is on the
> client.
>
> If, however, you are talking about uploading a file using upload.xsp to a
> directory that happens to also be available via webdav, it would just be a
> matter of specifying the correct directory in web.xml for upload-directory
> or whatever that param is called.
>
>
--------------------------------------------------------------------- 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]