A Bug of Seam Booking?

[riversider999]

First, login with user demo, repeat selecting several hotels , and you can see the selected hotel list in your workspace

Second, relogin with user gavin without logout, (by goback or input the login url), you can find the workspace is the same one of user demo.

The bug is that login does not clear the session before creating one.

[thejavafreak]

Post it in http://jira.jboss.org/jira/browse/JBSEAM and let's hope Jay will investigate it. Make sure you attach the test case also.

[jbalunas.jbalunas.jboss.org]

Good find - I just confirmed it.

To be clear this is what I'm seeing.

1. Login as demo - book a couple of hotels. 


2. Use the back button (either many times, or logout, login again and then back button) to get back to the login page.


3. Login as gavin


4. the booked hotels for demo are still showing

As an extra note any active workspaces for demo are cleared out - such as multiple unfinished bookings.  Only the booked hotels are still being seen.

This is mostly just a bug in the example, and not in seam itself, but either way thanks for letting us know.

Have you put a jira in?

-Jay

[btonez]

Not to be pessimistic, but are you sure that this isn't a sign of a larger problem with Seam, that the session is never being invalidated, so all session-scoped components are still alive?

[jbalunas.jbalunas.jboss.org]

I not worried that the session will never be invalidated, it will be cleaned up like any other session. 

I believe this is an application issue with the booking example managed its contexts and how it handles login conversations.  I have not a chance to look deeper through.

Do you have any specific concerns, or more information?

[norman]

What version of Seam is this?  I attempted this using trunk and was not able to reproduce the problem.

[riversider999]

Just posted.

http://jira.jboss.org/jira/browse/JBSEAM-3127

[jbalunas.jbalunas.jboss.org]

I verified with 2.0.3.CR1

[jbalunas.jbalunas.jboss.org]

Thanks

[norman]

Actually, the relogin isn't really happening.  The faces message being displayed is bad. This issue only affects 2.0.  See the notes on the JIRA issue for more detail.