Robert Koberg wrote:
>>The problem is conceptual, that document() breaks SoC, as described at
>>http://localhost:8787/cocoon/documents/faq/faq-xslt.html#faq-6 Hopefully
>>things like XPathTransformer will remove the need for document()
>>altogether.
>
>
> Yea, I have heard the argument.
>
> I just don't understand why you can't use XSL to separate out some these
> concerns.
Don't use Cocoon then, use XSLT.
You can use XSLT extensions instead of the DB Generator, make your own
extensions instead of XSP taglibs or use document() for aggregation.
Why use Cocoon at all?
> Hmmm... one line of XSLT v. (at least) one class
>
> Perhaps (the general) you could create a 'business-logic' directory and put
> these 'worker' XSLs in it to avoid the cognitive dissonance.
>
> XSL has many uses, why psuedo-cripple it?
You need the right tool for the right job.
This transformer, if done well, can be faster, more efficient than xslt,
which is more general-purpose.
Anyway, it isn't compulsory, you can use whatever you prefer.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
