Hi Johannes,

>I can't quite understand why one should create a whole 
>XML tree in flow script. isn't it much easier to use JXT 
>for this purpuose ? 

I m using XSL Stylsheets to generate a PDF file. Dependant on the called URI
basicly three different things can happen with the generated PDF.
1. It is send back to the client and showed in ist browser.
2. It is stored in a Database and will not be send to the client. Only the
status XML is send back.
3. It is copied into a directory and will not be send to the client. Only
the status XML is send back.

All three Jobs are using the same Styleshteets. I just want to stylsheets to
generade PDF files and not to contain any Job logic. This is why I have the
job logic somewhere else.

I m using cocoon.processPipelineTo() in the script.
// calling cocoon pipeline using processPipelineTo() method and dumping the
results to the outputstream
cocoon.processPipelineTo( pdf_uri, null, outstreamPDF );

How could I use this to generate a XML file?

Regards,
Jan


-----Ursprüngliche Nachricht-----
Von: Johannes Textor [mailto:[EMAIL PROTECTED] 
Gesendet: Montag, 26. September 2005 16:29
An: users@cocoon.apache.org
Betreff: Re: Flow Script Output

Hi Jan,

[EMAIL PROTECTED] schrieb:

>This method has some seriouse drawbacks. 
>First and most important for me is, that it look quite silly. I think 
>it is not supposed to be done this way. Would'nt it be much smarter to 
>just drop the XML into the result stream that is send to the client 
>anyway than to save it on disk?
>  
>
I can't quite understand why one should create a whole XML tree in flow
script. isn't it much easier to use JXT for this purpuose ?
You have two choices to save the XML that is sent tho the client on the
server's hard drive:

- use the sourcewriting transformer
- use cocoon.processPipelineTo()

Regards,
Johannes

---------------------------------------------------------------------
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]

Reply via email to