M
> To: [EMAIL PROTECTED]
> Subject: RE: [OS-webwork] Further weirdness with the valuestack and
> modeldriven
>
>
> Here it is. "getSession()" is returning a thread local session object.
> The Manager class is a class encapsulating data access.
>
> from
ut that call, the updated model isn't on the stack.
>
>
> Let me know if this clarifies things.
>
> -----Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Jason Carreira
> Sent: Wednesday, November 12, 2003 12:40 PM
> T
rther weirdness with the valuestack and
modeldriven
Please post your Action code... I'm suspecting it's 4)
> -Original Message-
> From: Drew McAuliffe [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, November 12, 2003 3:36 PM
> To: [EMAIL PROTECTED]
> Subject: [OS-webwo
Please post your Action code... I'm suspecting it's 4)
> -Original Message-
> From: Drew McAuliffe [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, November 12, 2003 3:36 PM
> To: [EMAIL PROTECTED]
> Subject: [OS-webwork] Further weirdness with the valuestack
>
In a recent message, I described a problem I had with the model object of a
ModelDriven action. The model object is pushed onto the top of the stack by
the ModelDrivenInterceptor but after updates to the model in the action, the
value at the top of the stack isn't the same as the updated model.
I'
