Good question. ATM, I only could give artificial scenarios.
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). 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.
Sven
Andrew C. Oliver schrieb:
> Explain, elaborate.
>
> 2 Why would you want to do it at the transformation point?
>
> Sven Kuenzler wrote:
>
>> Something that just came to me thinking of the dicussion about an
>> ExcelGenerator: What about implementing it as (Writeable)Source
>> instead? That way you could use it with SourceWritingTransformer and
>> friends, not only as pipeline starting point.
>>
>> 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]>
>>
>>
>
>
>
>
> ---------------------------------------------------------------------
> 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]>
>
>
---------------------------------------------------------------------
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]>
