Many thanks, for the clarification.
Peter
- Original Message -
From: "Howard Lewis Ship"
To: "Tapestry users"
Sent: Friday, 6 March, 2009 01:06:39 GMT +02:00 Athens, Beirut, Bucharest,
Istanbul
Subject: Re: Tapestry 5.1 session invalidate misbehaving
HttpServletRe
>
> Robert
>
>> Cheers,
>> Peter
>>
>>
>> - Original Message -
>> From: "Peter Stavrinides"
>> To: "Tapestry users"
>> Sent: Thursday, 5 March, 2009 09:59:29 GMT +02:00 Athens, Beirut,
>> Bucharest, Istanbul
>
uot;
To: "Tapestry users"
Sent: Thursday, 5 March, 2009 09:59:29 GMT +02:00 Athens, Beirut,
Bucharest, Istanbul
Subject: Re: Tapestry 5.1 session invalidate misbehaving
Thanks for the reply Robert, but that doesn't seem to be the issue,
any other ideas?
- Original
02:00 Athens, Beirut, Bucharest,
Istanbul
Subject: Re: Tapestry 5.1 session invalidate misbehaving
Thanks for the reply Robert, but that doesn't seem to be the issue, any other
ideas?
- Original Message -
From: "Robert Zeigler"
To: "Tapestry users"
Sent: Thurs
Thanks for the reply Robert, but that doesn't seem to be the issue, any other
ideas?
- Original Message -
From: "Robert Zeigler"
To: "Tapestry users"
Sent: Thursday, 5 March, 2009 00:45:14 GMT +02:00 Athens, Beirut, Bucharest,
Istanbul
Subject: Re: Tapest
Try switching the order of homePage.setIsSignOut(true) and
request.getSession(false).invalidate();
It looks like the homePage is being lazily evaluated right there, and
the page load is failing; if you switch the order, I think you'll be
set.
Robert
On Mar 4, 2009, at 3/48:39 AM , Peter St
Hi,
The following code worked in all versions before 5.1, but now I get the
exception listed below:
@Inject
private Request request;
@InjectPage
private Home homePage;
@OnEvent(component = "signOut")
Object onEventFromSignOut() {
try {
