cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Charles Yates <>
Subject Re: roll your own serializer
Date Sun, 11 May 2003 17:35:35 GMT
    I'm not sure what you mean by 'used entirely as a parameter format 
structure'.  Could you explain that more?  Anyway, unless I am mistaken 
the answer to your question is no.  As I understand it serializers 
contract is just to turn SAX events into a character stream and set a 
mime type.  Any tweaking of the events should be occuring in a 
transformer.  Maybe you should roll your own transformer?


Jorg Heymans wrote:

> Hi,
> I have the following pipeline in sitemap.xmap, added numbers for easy 
> reference ;)
>     <map:pipeline>
>     1)<map:match pattern="/specialrequest"/>
>     2)<map:generate type="request"/>
>     3)<map:transform src="specialrequest.xsl"/>
>     4)<map:serialize type="customserializer"/>
>     </map:pipeline>
> The serializer i wrote implements the "Serializer" interface. I am 
> writing it because i need to stream back a content type that is not 
> covered by the existing serializers.
> The mechanism generally works...
> *but*
> The output of the XSL transformation in 3) is an XML document, this 
> document needs to be used entirely as a parameter format structure for 
> a service within the serializer in 4). The serializer class receives 
> the XML as SAX events however, so I need to reconstruct the full XML 
> document from these events. I was hoping to avoid this.
> Is there a way to access the full XML document from the serializer class?
> Kind Regards
> Jorg Heymans
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message