On 4/30/08, Carlos Tejo Alonso <[EMAIL PROTECTED]> wrote:
> > Would you explain the use case? Perhaps we can find another
> > way to solve
> > it. :)
> We have an .xml file (in.xml) in the input and we want "defrag" it in
> several .xml (out-1.xml, out-2.xml, out-3.xml) files
> Carlos Tejo Alonso
Questions:
Are you using Cocoon for a Web request or just a file-to-files operation?
Is the input file being submitted or does it already exist on the server?
Should the output files remain on the server or are they only needed
fro the response?
If file-to-files, the SourceWritingTransformer will produce multiple
files. The response should confirm success and give the directory
name where the output files were created.
A Web request has several options:
1. Create the files with the SourceWritingTransformer, then return a
page of links to the new files. This option leaves the output files
on the server so a cleanup routine may be desirable -- use another
link ("Remove output files") and/or a scheduled process.
2. Create a single response using the SourceWritingTransformer and the
ZipSerializer, returning a ZIP file containing all the output files.
This option is best when you know the users have (and know how to use)
an unzip program.
3. Create each output file on-demand. The Web request specifies a
number and Cocoon responds with just the output file for that number.
The first response could return a page of links; the difference from
#1 is the response files are not created until the single-output
request is processed. This option is best if people typically only
need one of the output files.
solprovider
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
