Jason Johnston wrote:
On Tue, 2005-08-02 at 16:14 +0200, Sylvain Wallez wrote:
Because you should really avoid using JXTransformer if you want a
responsive application: this transformer basically feeds the JX
generator with the incoming SAX stream, meaning the template is full
reparsed and recompiled at each execution, which is highly inefficient.
IMO, we should make this very prominent in the doc and discourage such
usage, or even deprecate this transformer.
Ah, I wasn't aware of that. This should definitely be prominently
documented.
Would it be possible to use Cocoon's caching mechanism to improve this
situation, i.e. if all the pipeline stages prior to the JX transformer
are cacheable and valid, then a compiled JX template gets used?
Easy: split your pipeline and use <map:generate type="jx"
src="cocoon:/part-before-jx-generator"/> !!
Sylvain
--
Sylvain Wallez Anyware Technologies
http://people.apache.org/~sylvain http://www.anyware-tech.com
Apache Software Foundation Member Research & Technology Director
