You could add the generated parameter to the parameters map through your
interceptor.
S
On Thu, Mar 6, 2008 at 7:22 AM, GF <[EMAIL PROTECTED]> wrote:
> On Thu, Mar 6, 2008 at 1:52 PM, Adam Hardy
> <[EMAIL PROTECTED]> wrote:
> > I didn't see the second half of your message until I'd sent that.
>
>
> > What calls to the setters are you asking about? Do you mean any random
> property?
> > Are you talking about HTTP parameters?
>
> In few words, I have a property (let's imagine a String to keep it
> simple) in my action.
> The interceptor generates in some way a String object.
> Finally the interceptor should try to "push" inside the Action object
> that property,
>
> I think that is the same logic used by the StaticParameters
> interceptor, it checks if that "property setter" exists in the action,
> and in that case, the setter is called.
>
> The idea about making the action implementing an interface and than
> checking it with "instance of" is good, and I think it can do the
> trick, i still have to try it on my code.
>
> My thought was to do something similar to what happens when i pass
> with POST/GET some data to my action.. i.e. my.action?var=value
> I think it checks if setVar(..) exists and then it calls setVar(new
> String("value")) or something like that.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Scott
[EMAIL PROTECTED]
