This may sound a tad bit bizarre, but it looks like I could define a fairly generic layout with sections for "header", "nav", "body", "footer", etc. Each section can use import uri="cocoon:something" to generate that section. In turn jxtemplate generator can be used in those to create subsections, etc. This is a lot like what we do with XSLT although we create the separate parts through aggregation and then use a layout stylesheet to put it all together.
Does this seem realistic and might it perform better than XSLT? In both cases (for us) the header, nav, and footer are constant but the body (or a part of it) changes with every request. Ralph -----Original Message----- From: Sylvain Wallez [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 05, 2004 2:33 PM To: [EMAIL PROTECTED] Subject: Re: JXTemplate performance JXTemplate as a transformer certainly runs way slower than XSLT, since the template being the input of the transformer, its compilation occurs for every request. Also JXTemplate isn't cachable both in its generator and transformer incarnations. Sylvain -- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
