On 18.05.2004 10:22, Meyer, Christian wrote:
thanks a lot, that was my idea too, but it seems not very elegant, but up to
the upgrade it is okay.

Have a look on the 3rd recommendation! If you use Cocoon 2.0.4 or even the stuff from cocoon-2.0 CVS aka 2.0.5-dev it's absolutely valid to switch to the interpreted sitemap, i.e. it's stable. You can do this in the cocoon.xconf. We did this for our Conweb project that uses 2.0.4 too. The interpreted sitemap is not only faster at first request and each following request (at least with JDK 1.4 because of its runtime optimizings, don't know exactly with 1.3), it also gives better error messages. And if you can solve your current issue without an additional postprocessing it's one more reason to try the switch.

Just my 0.02 €.

Joerg

Here's a few options:

(3) The treeprocessor is available in 2.0, but not switched on by default. See if you can work out how to switch to an interpretted sitemap from compiled. This should give you the option of escaped \{ within a 2.0 sitemap.




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



Reply via email to