Andrew C. Oliver schrieb:
>> The real use case I had in mind was the application where I used the
>> Serializer out of Cocoon. This application produces an Excel sheet
>> which is sent out by Email. So it is not direct a response but a "side
>> effect" to the request. In C2 this is called a "sink" (or will be).
>
> Okay I got that part...but it sounds kind of like an action to me.
Well, haven't thought of that (yet). My other idea was about the yet to
be flow script system. Stefano gave an example save2disk() flow that
would be able to save a resource defined by sitemap to disk (so what?).
This was in the vision department of his RT, however. So I don't expect
this soon to be possible.
>> If I wanted to port that app to Cocoon, I thought of using a
>> Transformer. Then again, probalby I would not really need a
>> WriteableSource for that. IIRC, there is a Transformer which could
>> take a Serializer to produce the Excel output.
>
>
> Okay so the issue is that you have *two* outputs of sort. One is to
> email, one is to the browser. The Excel is to email and probably HTML
> to the browser.
The other part really is a SOAP response. Which isn't possible with C2
either. Or at least not as easy as with Axis and friends.
Sven
> In my mind this doesn't justify *breaking* the logical model of the
> sitemap. It seems you need an Action that makes a seperate internal
> request of sorts and emails the output. So the action would make a
> request to a different pipeline and email that, where the user response
> would be in HTML.
>
> Does that not sound reasonable? Any thoughts from you Vadim?
>
>>
>> Sven
>>
>>
>>
>>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
