cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Fagerstrom <dani...@nada.kth.se>
Subject Re: [jira] Commented: (COCOON-2110) Evaluate expressions defined in cocooon-expression-language-api in Sitemap engine
Date Mon, 13 Aug 2007 20:47:04 GMT
Grzegorz Kossakowski skrev:
> Joerg Heinicke pisze:
>> I wonder what exactly will it be when everything is unified: {} or 
>> ${}? I thought it's the latter, also the issue description seems to 
>> point on this.
> 
> The latter one because it's already used in Template and this way new 
> expressions can be evaluated alongside old ones. This way we can provide 
> smooth migration path.

As I wrote about in 
http://marc.info/?l=xml-cocoon-dev&m=118683052219287&w=2 we already 
(since maybe two years ago) has a migration path from the old to the new 
syntax. As the string template readers in template is plugable. In that 
implementation we actually use {} for the new syntax (following XSLT) as 
people seemed to prefer that back then. This is of course not written in 
stone, we could use ${} instead if that is what people prefer now. If we 
use ${} we more or less have to have JEXL as default expression language 
implementation, otherwise it will be highly confusing.

/Daniel


Mime
View raw message