Peter Hunsberger wrote:
On 10/10/06, Vadim Gritsenko <[EMAIL PROTECTED]> wrote:
Peter Hunsberger wrote:
> On 10/9/06, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
>
>> > But just adding all this stuff to request attributes is not that
>> > easy as
>> > unfortunately sub request are sharing the attributes with the main
>> > request. So whenever you use the cocoon protocol the main request
>> > and
>> > the sub request use the same set of attributes.
Sub request by definition is the separate Request object with own set of
attributes (potentially with ability to access parent or global request
attributes - via special convention, may be?). Once sub request is
completed,
all sub request attributes shall be discarded, leaving environment
only with
parent attributes. Does it make sense?
It's the bit about "potentially with ability to access parent or
global request" that seems to be the issue really isn't it? I can't
see how this would be optional?
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".
This is similar to current wrapper behavior for parameters:
public String getParameter(String name) {
String value = this.parameters.getParameter(name);
if (value == null && this.rawMode == false)
return this.req.getParameter(name);
else
return value;
}
Vadim
