A problem that I ran into was that Serializers do not have access to the environment (Request / Response). This means that it is very hard to write sophisticated Serializers.

We worked around this by using it in conjunction with a Transformer that was given the environment and simply passed it on to the Serializer.

Stefano Mazzocchi wrote:
Nicola Ken Barozzi wrote:



Stefano Mazzocchi wrote, On 18/03/2003 13.05:

Nicola Ken Barozzi wrote:


...

So, how would you tackle the above real-world problem?



I would not write a transformer but a serializer. In fact, a chart package image rendere *is* a serializer, since the output of a chart transformer will not need to be further processed anyway.



Hmmm, this seems different from you have said till now AFAIK. Wasn's a serializer just an "adaptor"?


Yes, an adaptor between an xml-driven inside and a binary-driven outside. It receives xml and produces binary. It receives an xml description of a chart and produces the raster image.

What's wrong with this?



I cannot configure it.


???? serializers are configurable just like any other component.

Stefano.






Reply via email to