Howard,
I have found ways around this problem for my special requirements. But I ran
into this problem on two occasions now in the last 10 days. And I think this
could happen to other people too.
Question is whether this is a bug in tapestry or at least something to be noted
in the documentatio
So, if you are trying to handle page access restrictions rather than
overall access restrictions, you can contribute into the
ComponentRequestHandler pipeline service, which comes later in the
process, after the request has been identified as either a component
event request (including things like
Am 29.10.2010 um 16:24 schrieb Thiago H. de Paula Figueiredo:
> On Fri, 29 Oct 2010 12:14:18 -0200, Moritz Gmelin
> wrote:
>
>> Hi,
>
> Hi!
>
>> It happened to me again that one of my RequestFilters was creating a
>> SessionStateObject. Which, when done for all assets of a page simply fails
On Fri, 29 Oct 2010 12:14:18 -0200, Moritz Gmelin
wrote:
Hi,
Hi!
It happened to me again that one of my RequestFilters was creating a
SessionStateObject. Which, when done for all assets of a page simply
fails at one point. Different Threads accessing different Assets in
parallel star
Hi,
It happened to me again that one of my RequestFilters was creating a
SessionStateObject. Which, when done for all assets of a page simply fails at
one point. Different Threads accessing different Assets in parallel start to
create new Sessions and thus the SSO gets lost.
Now one can resolve
