Meant to provide an example of their configuration and use:

http://tiles.apache.org/2.2/framework/tutorial/advanced/el-support.html


On Thu, Sep 12, 2013 at 9:34 AM, Ken McWilliams <ken.mcwilli...@gmail.com>wrote:

> I like the way Apache Tiles handles EL, from a user standpoint. I think
> everywhere an expression can occurs an AtributeEvaluatorFactory determines
> which registered ELEvaluator to used based on prefix, IE: "OGNL:" or "EL:".
> This could be extended to pattern matching too. Regex vs NamedVariable for
> instance, that would be nice.
>
> I don't think Apache Tiles allows for the assigning of a default? If it
> does I've been explicitly stating it everywhere... if there is no
> recognized prefix assuming a default of OGNL would provide a measure of
> backwards compatibility (if not very reasonable backwards compatibility), I
> don't think many people start current expressions with "MVEL:" for
> instance...
>
>
> On Thu, Sep 12, 2013 at 4:29 AM, Christian Grobmeier 
> <grobme...@gmail.com>wrote:
>
>> Am 12.09.13 11:35, schrieb Lukasz Lenart:
>> > Hi,
>> >
>> > I have spent some time on MVEL replacement for OGNL and what I can say
>> > it will allow to clarify few things - like dependencies or overused
>> > conversion and so on. The real problem is with Xwork itself as it
>> > doesn't support plugins so it's a bit hard to replace OGNL in all
>> > places.
>> >
>> > And it would be good to have a choice - use OGNL or MVEL - just drop
>> > in a jar :-)
>>
>> Awesome!
>>
>> I looked into MVELs code. My current main concern - active development -
>> is still there. Last commit in MVEL was before 2 years. But the code
>> looks more readable than OGNL actually and is better documented.
>>
>> Maybe one time in the future we can make an attempt to extract the hard
>> xwork dependency to OGNL and support both languages.
>>
>> >
>> >
>> > Regards
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
>> For additional commands, e-mail: dev-h...@struts.apache.org
>>
>>
>

Reply via email to