Re: action variables persisting across invocations

2008-01-18 Thread Laurie Harper
Dave Newton wrote: --- Chris Pratt <[EMAIL PROTECTED]> wrote: Make sure you set scope="request" on your Spring action beans or it will create only one instance of the bean and reuse it forever. Is that better than setting scope="prototype"? Equivalent in this case AFAIK, since Struts will cr

Re: action variables persisting across invocations

2008-01-18 Thread Laurie Harper
Dave Newton wrote: --- Laurie Harper <[EMAIL PROTECTED]> wrote: Dave Newton wrote: --- Chris Pratt <[EMAIL PROTECTED]> wrote: Make sure you set scope="request" on your Spring action beans or it will create only one instance of the bean and reuse it forever. Is that better than setting scope="

Re: action variables persisting across invocations

2008-01-18 Thread Dave Newton
--- Laurie Harper <[EMAIL PROTECTED]> wrote: > Dave Newton wrote: > > --- Chris Pratt <[EMAIL PROTECTED]> wrote: > >> Make sure you set scope="request" on your Spring action beans or it > >> will create only one instance of the bean and reuse it forever. > > > > Is that better than setting scope="

Re: action variables persisting across invocations

2008-01-18 Thread Dave Newton
--- Ted Slusser <[EMAIL PROTECTED]> wrote: > Yes. You've already solved the problem, but: (1) You only need to define your actions explicitly if you're wiring them manually. (2) Normally action beans are configured to the "prototype" scope (the current Spring plugin docs [1] are for Spring versio

Re: action variables persisting across invocations

2008-01-18 Thread Dave Newton
--- Chris Pratt <[EMAIL PROTECTED]> wrote: > Make sure you set scope="request" on your Spring action beans or it > will create only one instance of the bean and reuse it forever. Is that better than setting scope="prototype"? d. --

Re: action variables persisting across invocations

2008-01-18 Thread Chris Pratt
> On Jan 18, 2008, at 1:17 PM, Chris Pratt wrote: > > >> On Jan 18, 2008, at 1:02 PM, Dave Newton wrote: > >>> --- Ted Slusser <[EMAIL PROTECTED]> wrote: > I have a struts2 action that is having some parameters set by the > parameter interceptor. If I go to a second browser / computer an

Re: action variables persisting across invocations

2008-01-18 Thread Ted Slusser
Great. thanks. That worked once I added this to the web.xml org.springframework.web.context.request.RequestContextListener Does it 'throw away' objects per request? Is this a performance concern? What about object pooling, etc. I suppose it's easier to throw it away rather than

Re: action variables persisting across invocations

2008-01-18 Thread Chris Pratt
> On Jan 18, 2008, at 1:02 PM, Dave Newton wrote: > > --- Ted Slusser <[EMAIL PROTECTED]> wrote: > >> I have a struts2 action that is having some parameters set by the > >> parameter interceptor. If I go to a second browser / computer and > >> call the action I am seeing the same values on the Act

Re: action variables persisting across invocations

2008-01-18 Thread Ted Slusser
Yes. On Jan 18, 2008, at 1:02 PM, Dave Newton wrote: --- Ted Slusser <[EMAIL PROTECTED]> wrote: I have a struts2 action that is having some parameters set by the parameter interceptor. If I go to a second browser / computer and call the action I am seeing the same values on the Action that we

Re: action variables persisting across invocations

2008-01-18 Thread Dave Newton
--- Ted Slusser <[EMAIL PROTECTED]> wrote: > I have a struts2 action that is having some parameters set by the > parameter interceptor. If I go to a second browser / computer and > call the action I am seeing the same values on the Action that were > previously set. Is this the normal behav

action variables persisting across invocations

2008-01-18 Thread Ted Slusser
Hello, I have a struts2 action that is having some parameters set by the parameter interceptor. If I go to a second browser / computer and call the action I am seeing the same values on the Action that were previously set. Is this the normal behavior? Is there a way to turn it off? Do