Re: Execute and wait interceptor and calling an action more than once

turn with their respective results. i guess, this can also be used to separate the key. Thanks for responses. 2008/7/21 Dave Newton <[EMAIL PROTECTED]>: > --- On Mon, 7/21/08, Burak Doğruöz wrote: > > The constraint here is about ExecAndWaitInterceptor storing > > and returning m

Re: Execute and wait interceptor and calling an action more than once

ExecAndWaitInterceptor) with different parameters, there may be no certain result that which browser will show which request. Thanks 2008/7/21 Dave Newton <[EMAIL PROTECTED]>: > --- On Mon, 7/21/08, Burak Doğruöz wrote: > > I think, even with an ajax approach, concurrent requests >

Re: Execute and wait interceptor and calling an action more than once

So, how to override this ExecAndWiatInterceptor behaviour? Is it possible to map by some key other than action name? If we use wildcards while defining action mapping, can we bypass this constraint? This way we can call myAction1, myAction2 and myActionRandomN which trigger myAction.action. Does E

Re: Execute and wait interceptor and calling an action more than once

Thanks for your response, I think, even with an ajax approach, concurrent requests for same action would result in unexpected output as these actions are stored by same action name at background. So in fact this is not a presentation constraint but a processing constraint. We can neither prevent c

Execute and wait interceptor and calling an action more than once

Hi, Our application lets user to run 2 (or more) copies of same action at the same time (possibly with different parameters) in a frameset. In execute and wait interceptor documentation ( http://struts.apache.org/2.x/docs/execute-and-wait-interceptor.html), it says that execute and wait intercepto