> The main issue/question/hitch/dilemma now is to figure out how to > deal with the historical fact that values were stored in request or > session scope, but now are intended to be stored in the > ActionContext. As it is now, I have the ServletActionContext both > calling superclass methods (for storing the values in the > ChainContext) and putting things in the request or session scope. > This has possible synchronization problems in that the reads do not > test the request/session scope -- they assume that the context > already has the right value. Maybe it should skip the superclass > version and only move things in and out of the request and session > scopes.
Can we deal with a new attribute in the form-bean declaration ? If yes, we can add a scope attribute with request/scope(/application) scopes possibilities and if it not defined we use the historical behavior : session scope. It can be easier to implement by this way remindable forms or not. Just my two cents, Cedric --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
