On 1/18/06, Michael Jouravlev <[EMAIL PROTECTED]> wrote:
>
> On 1/18/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
> > On 1/18/06, Laurie Harper <[EMAIL PROTECTED]> wrote:
> > >
> > > It might be worth noting that the WebWork integration for Struts
> Action
> > > 2.0 will introduce another expression syntax, OGNL (?). But any
> > > investment you make now in JSTL will still be valid as JSTL should
> work
> > > in any JSP regardless of what framework you're using.
> >
> >
> > JSTL expressions are also universal in JSP 2.0 (you can put them
> anywhere,
> > not just in tag attributes of JSTL tags), and are a very similar to
> value
> > binding and method binding expressions in JSF.
> >
> > I would consider the JSTL tags to be successors for the Struts "bean"
> and
> > "logic" tag libraries, for the most part.  They do not deal with HTML
> tags,
> > however (although JSF tags do).
>
> Now, when JSF is part of J2EE, will JSP be improved or it will
> stagnate at JSP 2.0 level?


The version of JSF that goes into Java EE 5 is 1.2, and the corresponding
JSP version is 2.1.  Both are in proposed final draft status today, and are
unlikely to change much.

Because JSP 1.2 --> 2.0 was such a big change, there was not a lot of need
to fundamentally enhance JSP this time around.  Instead, most of the effort
was expended on unifying the expression language syntax and semantics
between JSF and JSP expressions (so that they always mean the same thing),
as well as extracting out the expression language programmatic APIs into a
separate package so that one could reuse this in a different context.

In particular I mean what you wrote about, that JSTL does not replace
> Struts html tags. That is, JSTL (1) does not generate element names
> that reflect hierarchy of backing beans, and (2) it does not process
> input by means of BeanUtils or something similar to stuff raw request
> parameters back into beans.
>
> Is something like this on a drawing board for a next JSP spec?


Nope ... that's what JSF is for :-).

Michael.


Craig


---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to