struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Husted" <>
Subject Re: [s2] Roadmap for the core taglib
Date Sun, 04 Nov 2007 23:32:20 GMT
The key point is that we don't have to demonstrate all the flexibility
in the examples that we post at the site. People who don't know what
choices to make, will look at our examples, and just follow those.

As to the examples we post, I would like to pick a stack that we can
all support, and use it to write "best practices" examples. For
example, I'm not a fan of JSP, but I do agree that we should use JSP,
because that's what everyone understands and can at least maintain.
And, if when we post  FreeMarker or Velocity examples, we should label
them as "alternatives". (Even though I personally prefer Velocity.)

And now that we have the JPA, I would also like to use it to power the
MailReader, and other examples, and maybe work on some Eclipse tools
to make it all quite painless.  Right now, everyone knows that
JPA/Hibernate, Spring, and Struts/JSP is the defacto industry standard
stack, and that's what we should use in our examples.

As to the rest of it, there's a saying in ASF circles: Let Darwin Decide.

No one here is compelled to support anything. If no one knows the
answer to a question, then the question doesn't get answered.
Likewise, if something doesn't work as well as it might, and no one
submits a patch, it doesn't get maintained. In the end, what gets
supported and maintained will be a function of what each volunteer
chooses to support and maintain.

It's also important to recognize that the flexibility is being born
out of actual need. OGNL is scary, and the templating system is
ongoing source of performance complaints. If we were making decisions
based on support effort, then these are the first two things that
should go.


On Nov 4, 2007 3:02 PM, Tom Schneider <> 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?
>  :)
> 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;
> 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:
For additional commands, e-mail:

View raw message