Re: [jira] Commented: (COCOON-2110) Evaluate expressions defined in cocooon-expression-language-api in Sitemap engine

2007-08-17 Thread Grzegorz Kossakowski
Daniel Fagerstrom pisze: One of the points with plugability is that you can have several implementations of the interface ;) ;) I suggest that you leave LegacyStringTemplateParser as it was before and put your new code in a LegacySitemapStringTemplateParser that only is used in the sitemap.

Re: [jira] Commented: (COCOON-2110) Evaluate expressions defined in cocooon-expression-language-api in Sitemap engine

2007-08-17 Thread Daniel Fagerstrom
Grzegorz Kossakowski skrev: Daniel Fagerstrom pisze: Grzegorz Kossakowski skrev: Vadim Gritsenko (JIRA) pisze: Actually, such syntax is supported[1] in our code for almost two years now. The new syntax is supported but it is plugable and the default settings is using the old syntax. I didn

Re: [jira] Commented: (COCOON-2110) Evaluate expressions defined in cocooon-expression-language-api in Sitemap engine

2007-08-16 Thread Grzegorz Kossakowski
Daniel Fagerstrom pisze: Grzegorz Kossakowski skrev: Vadim Gritsenko (JIRA) pisze: Actually, such syntax is supported[1] in our code for almost two years now. The new syntax is supported but it is plugable and the default settings is using the old syntax. I didn't find any detailed design d

Re: [jira] Commented: (COCOON-2110) Evaluate expressions defined in cocooon-expression-language-api in Sitemap engine

2007-08-14 Thread Grzegorz Kossakowski
Daniel Fagerstrom pisze: 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 you see almost nobody has known that such migration path exists so, in a fact, there was not a

Re: [jira] Commented: (COCOON-2110) Evaluate expressions defined in cocooon-expression-language-api in Sitemap engine

2007-08-14 Thread Grzegorz Kossakowski
Daniel Fagerstrom pisze: Grzegorz Kossakowski skrev: Vadim Gritsenko (JIRA) pisze: Actually, such syntax is supported[1] in our code for almost two years now. The new syntax is supported but it is plugable and the default settings is using the old syntax. I didn't find any detailed design d

Re: [jira] Commented: (COCOON-2110) Evaluate expressions defined in cocooon-expression-language-api in Sitemap engine

2007-08-13 Thread Daniel Fagerstrom
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 eva

Re: [jira] Commented: (COCOON-2110) Evaluate expressions defined in cocooon-expression-language-api in Sitemap engine

2007-08-13 Thread Grzegorz Kossakowski
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. Th

Re: [jira] Commented: (COCOON-2110) Evaluate expressions defined in cocooon-expression-language-api in Sitemap engine

2007-08-12 Thread Joerg Heinicke
On 11.08.2007 6:23 Uhr, Alfred Nathaniel wrote: On Sat, 2007-08-11 at 11:22 +0200, Grzegorz Kossakowski wrote: Thanks for the summary, Grek. Speaking about myself I prefer much more language prefixes and I think we should go for it. The question that we need to answer is if we want to support

Re: [jira] Commented: (COCOON-2110) Evaluate expressions defined in cocooon-expression-language-api in Sitemap engine

2007-08-11 Thread Daniel Fagerstrom
Grzegorz Kossakowski skrev: Vadim Gritsenko (JIRA) pisze: Vadim Gritsenko commented on COCOON-2110: - Don't we have a history of using #{foo} for jxpath and ${foo} for jexl? Doing it differently would just result in more confusion. I'd rather have it mo

Re: [jira] Commented: (COCOON-2110) Evaluate expressions defined in cocooon-expression-language-api in Sitemap engine

2007-08-11 Thread Grzegorz Kossakowski
Hi Alfred, Alfred Nathaniel pisze: On Sat, 2007-08-11 at 11:22 +0200, Grzegorz Kossakowski wrote: Speaking about myself I prefer much more language prefixes and I think we should go for it. The question that we need to answer is if we want to support #{} syntax in sitemap? Since it was never

Re: [jira] Commented: (COCOON-2110) Evaluate expressions defined in cocooon-expression-language-api in Sitemap engine

2007-08-11 Thread Alfred Nathaniel
On Sat, 2007-08-11 at 11:22 +0200, Grzegorz Kossakowski wrote: > Speaking about myself I prefer much more language prefixes and I think we > should go for it. The > question that we need to answer is if we want to support #{} syntax in > sitemap? Since it was never > there I don't think it mak

Re: [jira] Commented: (COCOON-2110) Evaluate expressions defined in cocooon-expression-language-api in Sitemap engine

2007-08-11 Thread Grzegorz Kossakowski
Vadim Gritsenko (JIRA) pisze: Vadim Gritsenko commented on COCOON-2110: - Don't we have a history of using #{foo} for jxpath and ${foo} for jexl? Doing it differently would just result in more confusion. I'd rather have it more uniform throughout. Actu

[jira] Commented: (COCOON-2110) Evaluate expressions defined in cocooon-expression-language-api in Sitemap engine

2007-08-10 Thread JIRA
[ https://issues.apache.org/jira/browse/COCOON-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12519194 ] Jörg Heinicke commented on COCOON-2110: --- Public vs. private API does not stand a second sight. Request.getSess

[jira] Commented: (COCOON-2110) Evaluate expressions defined in cocooon-expression-language-api in Sitemap engine

2007-08-10 Thread JIRA
[ https://issues.apache.org/jira/browse/COCOON-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12519193 ] Jörg Heinicke commented on COCOON-2110: --- I neither can recall it. How this one came up, Grek? I'm in favor of

[jira] Commented: (COCOON-2110) Evaluate expressions defined in cocooon-expression-language-api in Sitemap engine

2007-08-10 Thread Vadim Gritsenko (JIRA)
[ https://issues.apache.org/jira/browse/COCOON-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12519191 ] Vadim Gritsenko commented on COCOON-2110: - I'm not sure I can recall this decision - to change the start cha

[jira] Commented: (COCOON-2110) Evaluate expressions defined in cocooon-expression-language-api in Sitemap engine

2007-08-10 Thread JIRA
[ https://issues.apache.org/jira/browse/COCOON-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12519186 ] Jörg Heinicke commented on COCOON-2110: --- The start chars of the expression changes to ${ for all expression la

[jira] Commented: (COCOON-2110) Evaluate expressions defined in cocooon-expression-language-api in Sitemap engine

2007-08-10 Thread Vadim Gritsenko (JIRA)
[ https://issues.apache.org/jira/browse/COCOON-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12519184 ] Vadim Gritsenko commented on COCOON-2110: - Don't we have a history of using #{foo} for jxpath and ${foo} for