Gianluca Morello wrote:

Sounds good,

i'm calling the SWT pipeline from flow with redirectTo.
I tried also processPipelineTo from flow, but i don't know how to setup a
correct outputstream parameter.
A null outputstream parameter is invalid. I don't need to process the output
of the swt.

Do you have any example how to use processPipelineTo?


With a serious hack, try using:
processPipelineTo("URL", new Packages.org.apache.cocoon.bean.CocoonWrapper.NullOutputStream());


Only I wouldn't like to rely on the existence of that implementation of a null output stream. If you like this approach, you might want to make your own (it isn't hard).

Regards, Upayavira

Thank you

Gianluca






----- Original Message ----- From: "Upayavira" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, December 22, 2003 12:36 PM Subject: Re: SourceWriting Transformer: how to redirect after writing files?




Gianluca Morello wrote:



Hi all,

i have a pipeline i which i use a sourcewriting transformer to write a
xml file.

I wish to be able to redirect to a new page  after writing the file.
After the writing of the file i have on the browser the output
message of the sourcewriting transformer.

There's a way to do that?



Not sure if there is. I would suggest a couple of approaches:
1) Use XSLT to transform the result of the SWT into your desired page
for the user (could include a <meta http-equiv="refresh"> style redirect)
2) Use the Flow processPipelineTo to write your source, and then send
another page using sendPage

Regards, Upayavira



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







--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to