struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Schneider (JIRA)" <>
Subject [jira] Commented: (WW-1785) Validator fails on an action that does not extend ActionSupport
Date Sun, 04 Mar 2007 15:03:16 GMT


Tom Schneider commented on WW-1785:

Actually looking at the JUnit test, AnnotationValidationInterceptorTest, this test is doing
exactly what you are trying to do.  It has a TestAction class that isn't extending ActionSupport
and this test works perfectly fine.  The method signature of this method is:

public String execute();

It looks like the interceptor is trying execute() first, then it tries get doExecute(), if
it doesn't find either of these methods, then the interceptor throws the original MethodNotFoundException.
 I can't think of why this interceptor is failing for you.  It might be helpful to debug into
the interceptor and just verify that the actionClass is correct.

> Validator fails on an action that does not extend ActionSupport
> ---------------------------------------------------------------
>                 Key: WW-1785
>                 URL:
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Actions
>    Affects Versions: 2.0.6
>         Environment: Windows XP
>            Reporter: Scott Stanlick
>         Assigned To: Tom Schneider
>             Fix For: 2.0.7, 2.1.0
> I had an S2 app working great until this morning when I changed my custom BaseAction
class to no longer extend ActionSupport.  I am getting the following exception and quietly
being directed to an incorrect Result.  I am receiving the validator message in the server
> 09:46:53,416 ERROR Login:279 - Validation error for password: is required.
> SEVERE: Servlet.service() for servlet default threw exception
> java.lang.NoSuchMethodException: actions.Login.execute()
> 	at java.lang.Class.getMethod(
> 	at org.apache.struts2.interceptor.validation.AnnotationValidationInterceptor.getActionMethod(

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message