Michael added the logout handler I was suggesting, and a
2.1.1-SNAPSHOT release is available from
http://www.localhost.nu/java/mvn-snapshot/
--
regards,
Robin
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.
On Aug 12, 2009, at 1:04 PM, Michael Gerzabek wrote:
Norman Franke schrieb:
The demo/sample app did work fine, but my non-trivial app fails
unless I add the explicit session.invalidate() call in my event
handler. I have no super classes, but I do use a layout component.
It's rather trivial
Norman Franke schrieb:
The demo/sample app did work fine, but my non-trivial app fails unless
I add the explicit session.invalidate() call in my event handler. I
have no super classes, but I do use a layout component. It's rather
trivial, providing a menu and two-column layout. Nothing fancy.
The demo/sample app did work fine, but my non-trivial app fails unless
I add the explicit session.invalidate() call in my event handler. I
have no super classes, but I do use a layout component. It's rather
trivial, providing a menu and two-column layout. Nothing fancy.
However, putting the
So. What does this mean?
Did the sample work for you - I mean without getting an exception?
And if yes, what project layout (Layout components, super classes, etc.)
do you use that gives the exception you mention? Where does the
stacktrace exactly come from?
Michael
Norman Franke schrieb:
I didn't when I ran the demo. Maybe one needs a layout component?
Norman Franke
Answering Service for Directors, Inc.
www.myasd.com
On Aug 12, 2009, at 4:07 AM, Michael Gerzabek wrote:
Why do I not get the exception?
I'm testing with tapestry-spring-security-sample application at [1].
Mich
> An: "Tapestry users"
> Betreff: Re: tapestry-spring-security-2.1.0 logout issue
> The JavaDoc on org.apache.tapestry5.service.Request states that
> "getSession(false)" should return NULL if the session is invalidated.
> This is not happening, it returns th
Why do I not get the exception?
I'm testing with tapestry-spring-security-sample application at [1].
Michael
[1] http://www.localhost.nu/svn/public/tapestry-spring-security-sample
Norman Franke schrieb:
On Aug 11, 2009, at 5:20 PM, Robin Helgelin wrote:
On Tue, Aug 11, 2009 at 17:46, Norman
On Aug 11, 2009, at 5:20 PM, Robin Helgelin wrote:
On Tue, Aug 11, 2009 at 17:46, Norman Franke wrote:
The JavaDoc on org.apache.tapestry5.service.Request states that
"getSession(false)" should return NULL if the session is
invalidated. This
is not happening, it returns the invalidated sessi
On Tue, Aug 11, 2009 at 17:46, Norman Franke wrote:
> The JavaDoc on org.apache.tapestry5.service.Request states that
> "getSession(false)" should return NULL if the session is invalidated. This
> is not happening, it returns the invalidated session.
>
> I think this is because tapestry-spring-secu
The JavaDoc on org.apache.tapestry5.service.Request states that
"getSession(false)" should return NULL if the session is invalidated.
This is not happening, it returns the invalidated session.
I think this is because tapestry-spring-security is using the
HttpServletRequest and thus the Http
When I try to logout via tapestry-spring-security-2.1.0 (as in the
example, logoutService.logout() in my event handler for the logout
link), I get this error all the time:
How can I logout without error and go back to the main page?
java.lang.IllegalStateException: setAttribute: Session alrea
12 matches
Mail list logo
