Re: Parameter interception

2007-06-26 Thread Dave Newton
--- [EMAIL PROTECTED] wrote: > Hey Dave, to you care to comment? Sure; might as well earn my pay today. Oh, wait. >> Do you know what the code would look like to get the >> id off the action? AFAIK ModelDriven just pushes the model on to the top of the stack, so the easiest would be to use the

Re: Parameter interception

2007-06-26 Thread stanlick
Hey Dave, to you care to comment? On 6/25/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Alright! Now we are getting somewhere. Do you know what the code would look like to get the id off the action? Scott On 6/25/07, Dave Newton < [EMAIL PROTECTED]> wrote: > > --- [EMAIL PROTECTED] wrote

Re: Parameter interception

2007-06-25 Thread stanlick
Alright! Now we are getting somewhere. Do you know what the code would look like to get the id off the action? Scott On 6/25/07, Dave Newton <[EMAIL PROTECTED]> wrote: --- [EMAIL PROTECTED] wrote: > > If you've implemented ModelDriven and it's returning the payrollUpdate, then this would

Re: Parameter interception

2007-06-25 Thread Dave Newton
--- [EMAIL PROTECTED] wrote: > > If you've implemented ModelDriven and it's returning the payrollUpdate, then this would be expected behavior: ModelDriven puts the model on the stack so its properties are available w/o prefixing. d. ___

Re: Parameter interception

2007-06-25 Thread stanlick
I have a PayrollAction class that extends BaseAction which has an id field. PayrollAction also contains a bean that contains an id field. The id fields are the Hibernate PKs. My BaseAction extends ActionSupport implements SessionAware, ModelDriven, Preparable. I have carefully observed the foll

Re: Parameter interception

2007-06-24 Thread Dave Newton
--- [EMAIL PROTECTED] wrote: > If I call an action with an id=20 parameter and that > action contains both a field called id and a bean > that contains an id field, both fields are being set > to 20. Does the parameter "setter" logic set > everything on the action object hierarchy that it can >

Parameter interception

2007-06-24 Thread stanlick
If I call an action with an id=20 parameter and that action contains both a field called id and a bean that contains an id field, both fields are being set to 20. Does the parameter "setter" logic set everything on the action object hierarchy that it can find with the same name? -- Scott [EMAIL