Carsten Ziegeler wrote:
Vadim Gritsenko wrote:
IIUC original issue was about adding "all request relevant information as
attributes of the request object". Since for sub request those will be
attributes of sub request, they will not interfere with parent request: sub
request's "objectModel" (or "flowContext", etc) will mask parent's completely
and thus won't allow modification of parent's "objectModel".
Unfortunately this is not the way it has been implemented. Currently the
sub request uses an own request object but *shares* the attributes map
with the parent request. And this means it can override and delete values.
I'm not sure if we can change this (if people are relying on this
behaviour it would break their code).
... we can, though, introduce new behavior for new "cocoon:" scoped attributes.
(Similarly, there is special processing going on for "cocoon:" prefixed request
parameters).
Vadim
