I remember I have faced the similar problem before with only just servlets. Previous problem was, had a servlet containing a class level variable which holded the data. When multiple users hit the servlet, then the response data was switched to the users.
Here, in the action class, there is an inner class, which has a object (obj) that contains all the data. I am thinking this may be causing the problem. This looks like similar to the problem mentioned above and as Dave mentioned (>>>>>Do you keep any non-synchronized user-specific info in an instance of a class that is only instantiated once (like a servlet or action)? That gets a lot of people even though it's in all the documentation). Any suggestions/inputs on this? Thanks. Croff ----- Original Message ----- From: "Dave Newton" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <user@struts.apache.org> Sent: Thursday, June 09, 2005 3:31 PM Subject: Re: Multiple user - problem > Ray Madigan wrote: > > >It is hard for me to believe you got past a single user with out resetting > >the properties, unless you only write to them. If you use the form > >properties to assist in populating your form, the properties need to be > >reset. > > > > > Well, if I'm hitting a form with existing values (like an 'edit' > operation) I'd load up the form using the BeanUtils, not reset, because > that doesn't strike me as an appropriate place to fill a bean with > values from a DB. Other than occasional checkbox games I've never > directly used the reset method. > > In the JavaDoc it clearly states that "The default implementation does > nothing. In practice, the only properties that need to be reset are > those which represent checkboxes on a session-scoped form. Otherwise, > properties can be given initial values where the field is declared." > > I've written four fairly major webapps using struts, have touched the > reset method maybe 2-3x (for checkboxes), and that's it. I have _never_ > seen a case where I've gotten any old values, including under > stress-testing with dozens of simulated users posting/reading unique > form values. > > I haven't thought about it much at all lately, though, I use > DynaValiatorActionForms almost exclusively. > > Dave > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
