Re: Problem with configured action method names and Testing Framework - Action Testing with configured method names is broken in struts-2.2.3

2011-06-17 Thread UV
Of course I configured a method with the same name and returning String?!? But this is about using the action test framework of struts on actions configured with a method name in the XML instead of using the default execute() (which I use as a workaround now) So changing the names I use in th

Re: Problem with configured action method names and Testing Framework

2011-06-16 Thread Lukasz Lenart
2011/6/17 UV : > When I try to test an action with a method="actionMethod" attribute > configured in a  StrutsTestCase > the AnnotationValidationInterceptor fails in getActionMethod#75 cause it > cannot find the method Try to name your method actionMethod instead of getActionMethod and of return t

Re: Problem with configured action method names and Testing Framework ===> StrutsTestCase cannot handle actions not calling execute()

2011-06-16 Thread UV
Hi, the setup is unit testing with maven + spring + struts using StrutsSpringTestCase super class (which is an extended org.apache.struts2.StrutsTestCase with access to spring config). So this is working well with actions not having the methodname configured. Whenever I do configure such a m

Re: Problem with configured action method names and Testing Framework

2011-06-16 Thread Maurizio Cucchiara
Hi, could you send the stacktrace exception/error? What are you using to execute your test (f.i. maven, eclipse, etc)? Maurizio Cucchiara Il giorno 17/giu/2011 02.09, "UV" ha scritto: > Hi, > > When I try to test an action with a method="actionMethod" attribute > configured in a StrutsTestCase >

Problem with configured action method names and Testing Framework

2011-06-16 Thread UV
Hi, When I try to test an action with a method="actionMethod" attribute configured in a StrutsTestCase the AnnotationValidationInterceptor fails in getActionMethod#75 cause it cannot find the method using the configured name on the proxy used in the testing framework. My only workaround so f