Hi Vladimir,
The state of view models is serialized into the OID, which in turn is part
of the URL. No HTTP session is involved. When an action is invoked upon a
view model, the framework obtains the OID from the URL, deserializes the
info and uses this to recreate the view model.
In the case
Hi Dan, thanks for your input, will try this out, although I didn't
understand yet how it helps.
I don't generally understand how is the lifecycle of view model, do you
hold them in server session, Or forward them marshalled to browser and then
back to server, or even both?
Alternatively I found
Hi Vladimir,
We hit this issue in Estatio too a while back. I have a solution which,
for some reason, is in the non open source bit of Estatio we have; not sure
why I put it there, will have to move it to the github side.
Anyway, try adding this:
@DomainService(nature =
Hi, my view models seems to be such large that I get now the exception
"Header is too large 8193>8192" when browser submits e.g. an action from
rendered view model to server running on jetty.
Is this a jetty-specific issue is has generally related with the fact that
view model is marshalled into
