Grzegorz Kossakowski wrote:
> Reinhard Poetz pisze:
>> Grzegorz Kossakowski wrote:
>>
>> If we follow your arguments, we would also have to forbid passing
>> request attributes to sub requests. IMO this is too strict because this
>> would cause a lot of overhead, e.g. what about our flow implementa
[
https://issues.apache.org/jira/browse/COCOON-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12547311
]
Antonio Gallardo commented on COCOON-2032:
--
Would you provide a sample for the cocoon demo?
> [PATCH] Sort
Reinhard Poetz pisze:
> Grzegorz Kossakowski wrote:
>> [EMAIL PROTECTED] pisze:
>>
>> Hi Reinhard,
>>
>> I would like to ask how your changes relate to
>> https://issues.apache.org/jira/browse/COCOON-1831 ?
>
> I was searching for this patch but didn't find it because it is a
> sub-task in Jira. L
Reinhard Poetz pisze:
> Grzegorz Kossakowski wrote:
>
> If we follow your arguments, we would also have to forbid passing
> request attributes to sub requests. IMO this is too strict because this
> would cause a lot of overhead, e.g. what about our flow implementations
> that allow passing data ob
Grzegorz Kossakowski wrote:
Reinhard Poetz pisze:
Carsten Ziegeler wrote:
Reinhard Poetz wrote: What happens if a sub request accesses the session?
Is an artifical one created?
The current implementation returns an unusable implementation of a session
which needs to fixed in some way.
After h
Grzegorz Kossakowski wrote:
> Reinhard Poetz pisze:
>
>> After have been using the servlet-service framework for about 1/2 a
>> year, I have to say that I haven't been missing the access to sessions
>> because a child-request shouldn't affect a parent request. Whatever it
>> has to return to i
Reinhard Poetz pisze:
> Carsten Ziegeler wrote:
>> Reinhard Poetz wrote:
>> What happens if a sub request accesses the session? Is an artifical one
>> created?
>
> The current implementation returns an unusable implementation of a
> session which needs to fixed in some way.
>
> After have been us
