Mmmh... careful here : you're relying on a unspecified behaviour that
allows a flow script to not send a page. And we still have to decide if
this allowed or not.
Let me also ask that you be careful too. It works....and my application depends on this behaviour. Allowed or not!
As I said on the dev list:
So long as you clearly document the new way of doing this, and leave the old way in place for at least one release cycle!
What do you think of the CopySourceAction I've added (see [1])? Doing the equivalent of your saveToFile.flow should be pretty trivial, no?
Mind you, given the state of Cocoon docs, that is a lot to ask, non? ;-)
Keep in mind that my application will be used by over 10K users at a huge brokerage firm....so breaking the current behaviour (even if it was not intended) would not be a "good thing" for Cocoon's reputation in the industry.
Congrats for your project. But I really think this unspecified behaviour you're using is not the good way to go. So let's keep it as is in the upcoming 2.1.3 and forbid it in 2.1.4.
Sylvain
[1] http://cvs.apache.org/viewcvs.cgi/cocoon-2.1/src/java/org/apache/cocoon/acting/CopySourceAction.java?rev=1.1&content-type=text/vnd.viewcvs-markup
-- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects } Orixo, the opensource XML business alliance - http://www.orixo.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
