cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Grzegorz Kossakowski <>
Subject Re: New expressions' syntax
Date Sun, 19 Aug 2007 21:39:44 GMT
Rainer Pruy pisze:
> Daniel Fagerstrom schrieb:
>> Grzegorz Kossakowski skrev:
>>> Daniel Fagerstrom pisze:
>> ...
>>> Simply choosing {} is not a solution because there will be no smooth
>>> migration path for two reasons:
>>>   a) some JX may break as proved above
>>>   b) it's all or nothing situation, if someone (or we) decides to
>>> switch to new expressions their existing applications simply break
>>> Such radical step has its own benefits but I'm not sure if it's
>>> exactly what you would agree with.
>> We are not forcing anyone to use the new unified ELs, we just offer
>> people to do that if they feel like it. It is just a configuration setting.
>> /Daniel
> Hmm, leaving me wonder, whether such configuration can be decided upon
> on a per block basis.
> Otherwise, if I'd choose using "new" EL I would be prevented from using
> blocks that stick to "old" world and vice-versa?

I'm not sure if we have mechanism for per block configuration but I fear you may be right.
main merit of Cocoon's (future) OSGi integration is blocks isolation.

That's why I had this intuitive to enable people mix old and new syntax. Any thoughts?

Grzegorz Kossakowski

View raw message