Gianugo Rabellino wrote:
Stefano Mazzocchi wrote:
Paul Duffin wrote:
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.
For example? (I think FOP and batik are both
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
Christian Haul wrote:
On 03.Dec.2002 -- 11:34 PM, Diana Shannon wrote:
I was trying to sync HEAD and release versions of
src/documentation/xdocs/userdocs/actions/database-actions.xml
but when I try to commit the updated version to the release branch, I
get:
cvs server: sticky tag `cocoon_2_0
I have some general questions on the design, the answer to many of them
may be that it is historical but I could not find anything in the code
to indicate this.
Please do not take these questions as criticisms, I am simply trying to
understand the design of the code. If there is a resource that
Carsten Ziegeler wrote:
Paul Duffin wrote:
Why is the Serializer not an instance of SitemapModelComponent when both
generators and transformations are ?
The following link shows a discussion which took place in April this
year which seemed to indicate that this was going to be changed but
Why is the Serializer not an instance of SitemapModelComponent when both
generators and transformations are ?
I realise that none of the existing Serializers actually need the
information which is supplied by the setup method and that if you are
not careful it is very easy to use the ServletRes
