Dave Newton on 05/02/09 16:47, wrote:
Adam Hardy wrote:
Tell you the truth, I don't really dig the idea of having to specify
parameter in config file like that - I think it adds another thing
that can go wrong when you're refactoring. And it also needs special
testing requirements.
What are the additional testing requirements? The returned result is a
string, the parameters used in the result config are strings--what's left?
The unit test must additionally set up struts to be aware of the config.
Junit4 / easymock to test the actions without any reference to the config
doesn't need that.
Perhaps it's trivial although I doubt it. The concept of putting that action
parameter into the config when it's not an initialization param blurs boundaries
and bends the KISS approach too far.
Regarding JSTL vs OGNL, again, the simplicity of JSTL is fine. When you need
something complex, write a taglib function for it - generally it's easier to
read in the JSP and the taglib code is testable.
HTTP and HTML is so messy even on its own, I think it's best to keep it as
simple as possible.
Just my PoV - coming from a generalist in coding right across the GUI / MVC /
Java / DB stack, rather than as a front-end specialist.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org
