There should be a default EL (OGNL) for backward compatibility. Any IDE
will show you API breakage changes but none of them will pickup changes to
tag string requirements changes in the JSPs!
It's probably a good idea to force the user to explicitly state the default
in struts.xml but such an option should be available.
It must be remembered for some peculiar reason people used to use "${}" for
OGNL in XML and annotations so when the effort gets to that level, a way to
define package level defaults might be a good idea too (default to OGNL
regardless even if ${} is encountered).
On Fri, Sep 13, 2013 at 2:14 AM, Lukasz Lenart <lukaszlen...@apache.org>wrote:
> 2013/9/12 Dale Newfield <d...@newfield.org>:
> > On Sep 12, 2013, at 11:34 AM, Ken McWilliams <ken.mcwilli...@gmail.com>
> wrote:
> >> prefix, IE: "OGNL:" or "EL:
> >
> > I've long argued that %{}, #{}, ${} provides this already, and that this
> wrapping should therefore not be optional in preparation for when something
> other than %{} might be functional.
>
> Easy you horses ... it's a complicated task ;-) First I'd like to have
> other implementation working, thus should eliminate some internal bugs
> (like additional conversion from parser - parser did that already :-))
> and internal dependencies.
> Next I want to change behaviour of all tags - there be no automatic
> expression evaluation at all - you must directly use ${}, %{}, #{} to
> do that - thus will eliminate users' frustration when to use $,%,# and
> when don't.
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
> For additional commands, e-mail: dev-h...@struts.apache.org
>
>
