>If you put it into session scope, then you only have threading issues if you allow a single user to invoke more then one thread in a session. The way to avoid that is >to use the request scope.
That's where we came from. On the other side, if you put the action form in the request form, after the first request, your data are gone. > a given form, with 'threading-related' issues (I'm thinking > of reset(), for > instance). Which > would be the advantage of having information stored in an > ActionForm object > stored in > the session, against, for instance, a value object stored in > the session? > However, I can > understand that for some applications this may be usefull. >With a value object, int, float double and any other non-string violates a common assumption with UI's. When a user types in an invalid value for a field, they >generally expect the invalid data to be returned as the the user typed it in... Writing the code to do this is certaily possible, and you're probably doing... but why >write code you have to maintain? This is a good point. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
