[s2] JUEL plugin (was Roadmap for the core taglib)

[Don Brown <mr...@twdata.org>]

Whoa, where did that one come from?  I was just begging for such a
plugin yesterday on #struts from Richard Burton, who is working on an
MVEL one.  I could see Struts 3 == new taglib + JUEL + robust rest and
codebehind.

As for the problem of so many combinations of plugins, I'm all for the
proliferation of plugins, but do think we need to not ship with two
plugins that solve the same problem.  For example, it would be
confusing to ship with two codebehind plugins or two expression
language plugins, especially since the latter could require its own
taglib.  The distribution we ship as official Struts 2 should stay
coherent and focused.

Don

On 11/5/07, Tom Schneider <sc...@gmail.com> wrote:
> Ted Husted wrote:
> > Don's also been doing some preliminary refactoring in XWork so that
> > the expression language can be made pluggable, meaning we would also
> > be able to plugin something else instead of OGNL.
> >
> > -Ted.
> You mean like JUEL?
> http://cwiki.apache.org/confluence/display/S2PLUGINS/JUEL+plugin  :)
>
> Thanks for the info Ted, that helps me out.  So looking down the road we
> might have:
> xml configuration or codebehind;
> new java taglib or current templating taglib;
> freemarker, velocity or JSP;
> OGNL, MVEL, or JUEL.
>
> I'm all for choice, but trying to support all those combinations might
> be challenging. I can just imagine the posts on the user list:
> "Um.. I'm using Struts 2 with the code behind and rest plugin and the
> java taglib in velocity with MVEL and my page doesn't display"
> I'm not saying we shouldn't persue these endeavors, but I think it's
> helpful to consider things from a new user perspective and decide if
> we're going to support every combination of technology.
> Tom
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org

Re: [s2] JUEL plugin (was Roadmap for the core taglib)

[Tom Schneider <sc...@gmail.com>]

Isn't that what Ted wanted?  A new plug-in a day for 60 days.  :)  I 
have one lined up for tomorrow.
Tom

Don Brown wrote:
> Whoa, where did that one come from?  I was just begging for such a
> plugin yesterday on #struts from Richard Burton, who is working on an
> MVEL one.  I could see Struts 3 == new taglib + JUEL + robust rest and
> codebehind.
>
> As for the problem of so many combinations of plugins, I'm all for the
> proliferation of plugins, but do think we need to not ship with two
> plugins that solve the same problem.  For example, it would be
> confusing to ship with two codebehind plugins or two expression
> language plugins, especially since the latter could require its own
> taglib.  The distribution we ship as official Struts 2 should stay
> coherent and focused.
>
> Do

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org

Re: [s2] JUEL plugin (was Roadmap for the core taglib)

[Chris Pratt <th...@gmail.com>]

On Nov 4, 2007 2:58 PM, Don Brown <mr...@twdata.org> wrote:

> As for the problem of so many combinations of plugins, I'm all for the
> proliferation of plugins, but do think we need to not ship with two
> plugins that solve the same problem.

I believe Struts already ships multiple plugins that solve the same
problem.  The View and the File Upload problems each have multiple
plugins.  I think the whole point is choice, and I don't see any
problem with shipping that choice as part of Struts.  Ted has also
championed a one-stop, "getting started" file that would contain a
single solution to each of the problems (with the exception of the
view), which I think takes care of the problem of confusing new users.
 But that's just one, non-committer's, opinion.
  (*Chris*)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org