struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christoph Nenning <Christoph.Nenn...@lex-com.net>
Subject Re: <s:param @value> does not accept expressions?
Date Wed, 18 Jun 2014 08:38:11 GMT
This could make very simple usecases overly complicated.

E.g. using just a textfield:

<s:textfield name="myActionMember" />


This is already OGNL. And OGNL is used for reading and writing.

How would you do this with EL (especially the writing part) ?



Regards,
Christoph




> That's the pattern I expect. One tag should expose what you need from
> Struts to EL -- the rest of the Struts tags should just be pure EL 
enabled.
> 
> 
> Cheers,
> Paul
> 
> 
> On Tue, Jun 17, 2014 at 10:06 AM, Christoph Nenning <
> Christoph.Nenning@lex-com.net> wrote:
> 
> > In my JSPs I have interactions with struts all the time so OGNL is
> > important for me.
> >
> > A pattern I use quite often is to get objects via <s:set> (OGNL) and
> > afterwards use them with EL/JSTL.
> >
> >
> >
> > Regards,
> > Christoph
> >
> >
> >
> >
> > > I believe my thoughts are similar. When I code, I explicitly try to 
be
> > > "OGNL free" in my JSP. There's no reason for me to use OGNL unless I 
am
> > > forced to via interaction with Struts. I do what I can do make sure 
my
> > JSP
> > > usage sticks with the EE standard.
> > >
> > >
> > >
> > >
> > > Cheers,
> > > Paul
> > >
> > >
> > > On Tue, Jun 17, 2014 at 9:55 AM, Aaron Johnson
> > <johnson.aaron5@gmail.com>
> > > wrote:
> > >
> > > > EL now supports many functions of OGNL. Would it make sense just 
to
> > replace
> > > > OGNL with EL? There doesn't seem to be much of a community around
> > updating
> > > > OGNL. The newer versions of EL have improved support for usage 
outside
> > of
> > > > the JSP environment. Is it possible to use EL in the other 
templates
> > > > (Velocity, Freemarker, etc)? It is very confusing to have to work 
with
> > > > multiple expression contexts (ValueStack lookups and JSTL) when
> > authoring
> > > > JSPs.
> > > >
> > > >
> > > > On Mon, Jun 16, 2014 at 11:12 AM, Paul Benedict 
<pbenedict@apache.org>
> > > > wrote:
> > > >
> > > > > Maybe we should have two versions of the tags? One that accepts 
EL
> > (and
> > > > > never executes OGNL) and another one that does. Quite honestly, 
I
> > have no
> > > > > use for OGNL inside of JSP.
> > > > >
> > > > >
> > > > > Cheers,
> > > > > Paul
> > > > >
> > > > >
> > > > > On Mon, Jun 16, 2014 at 11:05 AM, Paul Benedict
> > <pbenedict@apache.org>
> > > > > wrote:
> > > > >
> > > > > > That's disappointing that we're crippling the use of these 
tags. I
> > just
> > > > > > want to use EL for single evaluation. I don't need both OGNL

and
> > EL in
> > > > my
> > > > > > tags -- just EL.
> > > > > >
> > > > > >
> > > > > > Cheers,
> > > > > > Paul
> > > > > >
> > > > > >
> > > > > > On Mon, Jun 16, 2014 at 10:44 AM, Dave Newton
> > <davelnewton@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > >>
> > > > > >>
> > > > >
> > > > http://struts.apache.org/release/2.2.x/docs/why-cant-i-use-jstl-
> > > style-el-expressions-in-struts-tags.html
> > > > > >>
> > > > > >>
> > > > > >> On Mon, Jun 16, 2014 at 11:26 AM, Paul Benedict
> > <pbenedict@apache.org
> > > > >
> > > > > >> wrote:
> > > > > >>
> > > > > >> > Is this a bug? I cannot use an EL expression to set
the 
"value"
> > > > > >> attribute.
> > > > > >> > I don't understand why such a restriction exists. Thoughts?
> > > > > >> >
> > > > > >> > Cheers,
> > > > > >> > Paul
> > > > > >> >
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> --
> > > > > >> e: davelnewton@gmail.com
> > > > > >> m: 908-380-8699
> > > > > >> s: davelnewton_skype
> > > > > >> t: @dave_newton <https://twitter.com/dave_newton>
> > > > > >> b: Bucky Bits <http://buckybits.blogspot.com/>
> > > > > >> g: davelnewton <https://github.com/davelnewton>
> > > > > >> so: Dave Newton <
> > http://stackoverflow.com/users/438992/dave-newton>
> > > > > >>
> > > > > >
> > > > > >
> > > > >
> > > >
> >
> > This Email was scanned by Sophos Anti Virus
> >

This Email was scanned by Sophos Anti Virus

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message