I can't see your app, so I'm kind of flying blind here. But I do have a couple
of questions. I assume that the logout page is just a display telling them
they have logged out? Since you have already logged them out, it seems as
though anything else would be kind of futile. Any reason why you just don't
send them back to the login page? Or just redirect them to the home page and
allow the login page to come up that way? It isn't like clicking the home
link is ever going to send them anywhere else so it seems like kind of a wasted
effort. Same overall result, and there aren't as many pages to manage,
flow-wise.
I got a bit lost on the old user bean/new user bean/user principle
explanation. But it seems like the easiest way to have done this would be to
simply invalidate the session and allow the next authentication to create the
new user bean the same way as would occur at first login. I assume you are
allowing JSF to manage them at session scope. As I said, I'm having kind of a
hard time following the exact steps, but the thing to keep in mind here is that
when you invalidate the session, you don't necessarily do away with any objects
that in in the session. If anything else has a reference to an object in that
session, it is still there in memory. So you may be running afoul of the
convention JSF is using the manage the bean instances.
As for the logout.jsp getting run through the faces servlet, what servlet path
is it configured for? If you are using the default and the url coming in is
<some context>/faces/<whatever> it is going through the servlet. Check the
path - again, not sure exactly what you are currently doing so not sure what to
tell you in terms of how to fix it. Mileage may vary.
I'm not a really JSF expert at this stage, but those are the kinds of things
I'd look at.
gn
---- Rich Schramm <richard.schramm@xxxxxxxxxxxxxxxxxx> wrote:
> Hello,
>
> I am creating a web app in JSF RI with richfaces and facelets. I have a
> session scoped managed been that stores preferences for the user who is
> signed in.
>
> The problem I am having is that when the user logs out. I invalidate the
> session and send the user to the logout page. On it's way to the logout
> page, it creates a new session for the user and instantiates the user
> managed bean again. The user lands at the logout page, then clicks the
> link to the home page. The system (properly) redirects him to the login
> page where he authenticates and goes to the home page. However, at that
> point the session is already there, so that he has the user principle of
> the new user with the User bean of the old user.
>
> I have, of course, checked to make sure that the logout page does not
> contain any reference to the User bean. In fact, I created a new home
> page with no reference to the user bean and the logout page has no
> reference to it, nor do the phase listeners. I actually commented the
> bean out of the faces config file and the modified home page / logout
> loop work fine without it (since it is not called anywhere). Once I
> uncomment it, the bean instantiates itself again. None of the other
> managed beans instatiate themselves with a new session, only this one
> (there are 2 others).
>
> I am sure I could work around this issue if I needed to, but I am trying
> to understand what is going on with this?
>
> On a separate but related note, I am having trouble making my logout
> page NOT be run through the faces servlet. It is in the same directory
> and same extension (.jsp) as my login.jsp page, and that page is not
> processed by the servlet, but logout.jsp is.
>
> BTW, we are looking to add another JSF/Portlet developer to our team.
> If you are interested let me know. If you are interested and can help
> me fix this, you are well on your way to a new job.
>
> Thanks,
>
> Rich
>
|