On Fri, Aug 31, 2001 at 06:24:08AM -0700, Davanum Srinivas wrote:

> As i answered earlier, you can inject a transformer in between that will resolver 
>the relative
> URL's and pump in the absolute url's just before your serializer is called. Will 
>this work?

It will certainly. Probably a plain XSLT transformation with some
string manipulation would be enough to make URLs absolute so 
there's even no need to write a custom transformer.

I'm still wondering, though, even after reading some mail 
archives, what's wrong inside the idea of Serializers being
part as a whole of the Cocoon system with access to the
execution environment: most probably I'm not
getting the point, but I can't see what would be wrong in 
having even those components know about the context they're
running into. Giacomo said in a previous thread:

> I'm still not conviced about the change and thus are -1 until someone
> come along with better arguments why a serializer need access to the
> environment.

My argument in favor of the setup() approach is that I just
banged my head against the wall of not being able to resolve
relative URLs. This is not allowing me to insert images inside
PDF files, just to cite an example. 

I'm not getting how putting another transformation
step instead of getting a parameter from the environment can
be a better solution: I tend to think that in the best case
it turns out into an error-prone, difficult to maintain
and redundant sitemap, if a serialization to some particular 
formats (actually any XSL:FO format as far as I can tell) 
needs a transformation just for being usable by the serializer.

I'm not arguing at all, actually I assume that if this has
been done on purpose and discussed there must have been a very 
good reason: I just would like to be enlightened on this
issue, since probably I'm not getting a basic point in the
Cocoon flow and design. Please shed some light. :)

Thanks again,

-- 
Gianugo Rabellino

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to