> second:
> I don't want to rain on your parade, but...
> from an architectural point of view: is
> "resolver.resolve("cocoon://dynamic-sql")" in XSP so much
> better than "document()" in XSLT ?
>
> Yes, the first is cached, and I agree (up to a point, though)
> that SQL queries belong to generation rather than
> transformation, but this resolver breaks the beauty of the
> sitemapm: having all pipelines pieces in one place.
>
It *is* cached, and (more important to me), I have a great deal of
control over the caching mechanism.... To get the same kind of control
with a transformer I have to subclass the transformer, which is (I
think) more work.
--Steve
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
