Re: Action chaining not forwarding ModelDriven model properties

2018-03-03 Thread Yasser Zamani
On 2/28/2018 3:47 PM, shahzad.ismail@ wrote: > I've debugged it a bit and able to figure out that, initially, at the start > of action1, request.getParamater("modelprop") is null then I set modelprop in > the action1 method which makes mymodel.modelprop == "something" and > request.getAttribut

Re: Action chaining not forwarding ModelDriven model properties

2018-03-01 Thread Lukasz Lenart
Can you share a source code of your actions? 2018-02-28 13:17 GMT+01:00 shahzad.ism...@gmail.com : > Hi, > I'm migrating an app from Struts 1 to Struts 2 (Tomcat v8 and Struts > 2.5.14.1). There is a scenario in which mapping goes like: > jsp1 --> action1 --> action2 --> action3 --> jsp2 > > So i

Re: Action chaining

2005-06-15 Thread Rafael Taboada
Finally I could call a method from an Action which extends LookupDispatchAction /BAction.do?method=myvaluekey where in my resources.properties file: key=myvaluekey Thanks to everybody for ur help =) -- Rafael Taboada Software Engineer Cell : +511-97753290 "No creo en el destino pues no

Re: Action chaining

2005-06-15 Thread Rafael Taboada
Thanks Michael for ur reply. I found this information I tried to follow: http://struts.apache.org/faqs/newbie.html#chaining But what about if BAction extends LookupDispatchAction I tried to use: /BAction .do?method=mymethod in the forward path but there is an error: javax.servlet.ServletE

Re: Action chaining

2005-06-15 Thread Michael Jouravlev
First off, there is no clear definition of what chaining is. Some say, that chaining is the process of transferring control strictly on the server (forwarding from action to action), thus linking action via redirect does not count as chaining :) Also there is an opinion that two actions do not make

Re: Action Chaining

2005-01-14 Thread Joe Germuska
At 11:36 AM -0800 1/14/05, Dakota Jack wrote: Hi, Joe, I think you sort of "punched the pouch" here. Let me explain. All your questions were answered in my posts, which you must have not read. Maybe you just read the first post and did not check out the later ones? must have passed each other in

Re: Action Chaining

2005-01-14 Thread Dakota Jack
Hi, Joe, I think you sort of "punched the pouch" here. Let me explain. All your questions were answered in my posts, which you must have not read. Maybe you just read the first post and did not check out the later ones? I have suggested an answer to cluster related behavior, if you read what

Re: Action Chaining

2005-01-14 Thread Joe Germuska
At 7:35 AM -0500 1/14/05, [EMAIL PROTECTED] wrote: Jack, You have said that LookupDispatchAction is outdated and inefficient. I have at a minimum 6 different actions that need to be performed per page, not including load. What else would you recommend as a solution? I'm not sure what the pe

Re: Action Chaining

2005-01-14 Thread Dakota Jack
Oops, try this! public abstract class StateBaseAction extends Action { private static final String DISPATCH_METHOD_SUFFIX = ".method"; private static final String EXECUTE= "execute"; private static final String PERFORM= "perform"; private static f

Re: Action Chaining

2005-01-14 Thread Dakota Jack
Hi, Todd, Check out: http://www.michaelmcgrady.com/button/. The DispatchAction there is unlike the one here. I use something close but a little different. Still, all you have to do is to give the property (name in HTML) the suffix you specifiy as the DISPATCH_METHOD_SUFFIX (see below). I use "

Re: Action Chaining

2005-01-14 Thread Todd_Nine
Jack, You have said that LookupDispatchAction is outdated and inefficient. I have at a minimum 6 different actions that need to be performed per page, not including load. What else would you recommend as a solution? Todd -

Re: Action Chaining

2005-01-13 Thread Dakota Jack
On Thu, 13 Jan 2005 09:37:47 -0500, [EMAIL PROTECTED] > Here is my problem, > > When the user clicks "previous" on the AnnuityAction, the previous method is > called. Previous saves the page, then forwards to /basic.do, which by default > will call load. I would begin by not doing this. I

Re: Action Chaining

2005-01-13 Thread Joe Germuska
At 1:58 PM -0500 1/13/05, [EMAIL PROTECTED] wrote: Sorry, I seem to have spoken too soon. The method paramater will have a value because the previous button has been pressed. I don't want to say we won't validate on previous or next, since we need to, I just need to not validate if struts is comi

Re: Action Chaining

2005-01-13 Thread Kishore Senji
Sounds like you need one more request parameter to distinguish between the a new request and a request coming after finishing an action. Token processing might be a good option which prevents the user from book marking. Do a saveToken() in the AnnuityAction. If the previous and next are form "sub

Re: Action Chaining

2005-01-13 Thread Todd_Nine
Sorry, I seem to have spoken too soon. The method paramater will have a value because the previous button has been pressed. I don't want to say we won't validate on previous or next, since we need to, I just need to not validate if struts is coming from another action

Re: Action Chaining

2005-01-13 Thread Todd_Nine
Thanks, I had soemthing similar in my parent form LaserForm, but that just checked for a query String on the request since we are bridging the old system to struts. I just never made the connection to check for the method parameter. Thanks for all the help. Todd

Re: Action Chaining

2005-01-13 Thread Kishore Senji
In your BasicForm's validate() you could do check for the "parameter"'s value and return "ActionErrors" based on that value; public ActionErrors validate(ActionMapping mapping, HttpServletRequest request){ /* if load or unspecified return null */ if(org.apache.commons.lang.StringUtils.isEmpty