cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carsten Ziegeler <>
Subject Re: Identifying expression language, Re: svn commit: r279283 - /cocoon/trunk/status.xml
Date Sun, 11 Sep 2005 09:26:15 GMT
Leszek Gawron wrote:
> It is not hardcoded, see
> src\blocks\template\trunk\WEB-INF\xconf\cocoon-template-expression.xconf:
> <expression-compilers>
> <component-instance 
> class="org.apache.cocoon.components.expression.jxpath.JXPathCompiler" 
> name="default"/>
> <component-instance 
> class="org.apache.cocoon.components.expression.jexl.JexlCompiler" 
> name="jexl"/>
> <component-instance 
> class="org.apache.cocoon.components.expression.jxpath.JXPathCompiler" 
> name="jxpath"/>
> </expression-compilers>
> So you can choose whatever prefix you like. Moreover you are are allowed 
> to use {expr} which will use default expression compiler. You've got it 
> even shorter than before.
Ok, you *can* change the prefixes but overall it's not a good idea. If
you are using the preconfigured values everyone knows what {jexl:ddd}
means, if you change the prefix to something else, you first have to
search through the xconf and see what the prefix means.

On the same topic, what about defining the default on a per template
base? For example havign a "default-expression-language-prefix" element
on top of the template?


Carsten Ziegeler - Open Source Group, S&N AG

View raw message