Thanks, Jorg! I got the point: It should be noted that there is no way to access any of the request, response, or context objects within a component that just implements this interface like the Serializer. The idea is to keep things simple. All your response attributes should have been already set, and the only responsibility at this point in time is to give the user what he wants--the rendered object (page/image/etc.).
What I have to do is prepare the SAX Stream in such a way (using a customized Transformer) that it holds all information that is necessary for the Serializer to work. I dont quite like that idea because it forces me to mix up document data with additional information in the xml which is only needed for processing the document data. Hm, I have to rethink the Serializer Design I think. --> I could pass the parameters during the Serializer configuration.. Drawback would be having multiple instances of the same Serializer with different parameters... Might work though. And would keep things explicit and simple. I'm gonna think about that, if you have further suggestions, I really liked to hear/read them! Michael >Michael Wirz wrote: > > > >>Former question in short: Why does Serializer not implement >>SiteMapModelComponent? >>Generator, Reader, Transformer do, Serialzer should! >> >> >> > >It's part of the design contract of a serializer. Have a look at >http://cocoon.zones.apache.org/daisy/documentation/writing/corecontracts/674.html > > >Jorg > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > -- abs IT Service GmbH abs gruppe Michael Wirz Entwicklung Landsberger Straße 57 82266 Stegen am Ammersee Telefon: +49 (0)8143 999 43 Telefax: +49 (0)8143 999 49 [EMAIL PROTECTED] www.eFonds24.de --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
