This changed when I pulled out the workflow from ActionSupport into the DefaultWorkflowInterceptor... You should either implement execute() or set your method in your xwork.xml to be doExecute() or whatever other method you want to call.
Sorry for the trouble, but it's for the greater good :-) > -----Original Message----- > From: Samuel Mota [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 18, 2003 11:05 AM > To: [EMAIL PROTECTED] > Subject: [OS-webwork] Action not beeing executed > > > Hi, > > I've just updated my Xwork/WW from the CVS this week (on > Thuesday I believe) and my actions are not beeing executed. > > All interceptors are beeing called > (StaticParametersInterceptor and ParametersInterceptor) at the > DefaultActionInvocation.invoke() but at my action call it > calls the ActionSupport.execute() instead of myAction.doExecute() ... > > why this behavior? > > Should by action (extending ActionSupport) declare the > execute() method OR the ActionSupport.execute > () should call the doExecute() method?!? > > In time ... the action reference is correct pointing to an > object of my class! > > thanks > > + Samuel G. Mota > + [EMAIL PROTECTED] > + 55 (11) 4417 7093 > + Business Application Dpt. > + Netset Serviços em Tecnologia > + a Hypercom Company > + http://www.hypercom.com > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
