Hi,
I need to perform database access for validation. Is the best place to do
this in my ActionSupport-derived class? If so, how can I mark which fields
have validation errors?
Thank you in advance for any advice.
*** IMPORTANT
NOTE* The opin
>Funny; I was thinking the same thing about the static context stuff in
JSF
>that makes it really difficult to test in isolation.
What makes you think that's difficult? I'm sure you're aware of mock
objects. There are a number of mock JSF test frameworks---JMock and Shale
come to mind. Writing
I wouldn't have seen that. Thanks, Jeromy. It's disturbing to see this
kind of code in 2008 and makes me wonder what other antipatterns might
exist in the struts2 codebase.
Dave Newton wrote:
> --- [EMAIL PROTECTED] wrote:
>
>> I'm curious why the developers of struts2 chose to define const
Hi,
I'm curious why the developers of struts2 chose to define constants in an
interface (StrutsStatics) and then implement that interface in at least 18
classes (see
http://struts.apache.org/2.x/struts2-core/apidocs/org/apache/struts2/StrutsStatics.html).
The"interface constant" pattern has b
Hi David,
Thanks again for the reply. I'm comparing MVC frameworks right now, and
wondering if struts2 has a similar feature to JSF. In JSF, an action can
look like this:
public class MyAction {
public String deleteUser() {
// Here I can inject errors for display on the JSP by writing:
5 matches
Mail list logo