Hi Cocoon devs,
I just noticed that the JX template generator uses a global object model
in the execution context. This leads to problems when multiple JX
template generators are called concurrently, e.g. if the processed
template contains includes:
<template>
${cocoon.parameters.foo} -> "foo"
<i:include src="…"/> (some JX generator, with parameter foo=bar)
${cocoon.parameters.foo} -> "bar"
</template>
The included JX template generator overwrites the cocoon/parameters
object in the object model, which affects the outer template.
Would it make sense to pass a copy of the object model to the invoker
instead of a reference to the global object model?
TIA for any comments!
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
