cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sylvain Wallez <sylv...@apache.org>
Subject Re: [Design] JXTG 2.0 (Just say yes!)
Date Mon, 06 Dec 2004 21:35:44 GMT
Vadim Gritsenko wrote:

> Sylvain Wallez wrote:
>
>> Vadim Gritsenko wrote:
>>
>>> Reinhard Poetz wrote:
>>>
>>>> IIRC we aggreed that we like the current syntax of JXTemplate. 
>>>> Exception: We deprecate the #{} notation in favour of ${xpath:....}.
>>>
>>>
>>>
>>> If nobody said this already (I have 150 or so mails to go ...),
>>
>>
>>
>> Yeah, cocoon-dev has gone crazy during the week-end :-)
>>
>>> more than one EL per template is clear FS to me. I'd be in favor of 
>>> specifying EL at the TemplateGenerator declaration time, and would 
>>> not go more granular than this.
>>
>>
>> I don't agree: it happens quite often to have mixed view data 
>> combining java objects and XML. In that case, a single EL is just 
>> painful.
>
>
> It just says a lot about state of the art in the expression language 
> arena but does not demonstrate a need for more than one! :)


Well, go back to the threads about ELs and check the ugly XPath syntax 
for object method calls chains and the impossibility to correctly 
traverse an XML document with Jexl!

>> Furthermore, specifying the language in the component declaration 
>> doesn't help readability nor reuse of templates between projects.
>
>
> If you don't see any better way out, I'd go as far as allowing to 
> choose EL in template itself, using attribute on the root element. I'd 
> not go further, though.


Mmmh... like XSP does...

BTW, isn't it you that added Python and JavaScript support to XSP? ;-)

Sylvain

-- 
Sylvain Wallez                                  Anyware Technologies
http://www.apache.org/~sylvain           http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }


Mime
View raw message