If you wait several minutes on search page, everything stops working.
Here is how you can repeat this behavior:
- all business operations are performed in one tab/window
- all debug operations are performed in second tab
1. register
2. login
3. search for string "a" - it works
4. check debug console - no conversations
5. wait 30 min. (this is actually around 5 min, but I don't now the exact number)
6. try searching for string "a" - it no longer works
7. click on search link at the top of the page
8. try searching for string "a" - it still doesn't work
9. click settings link at the top of the page
10. click on search link at the top of the page
11. try searching for string "a" - it still doesn't work
12. if you go to the debug console and inspect "user" from Session context you will see that it is null which, I guess, means that you are logged out of system
13. click settings link at the top of the page
14. try changing your password - you are (correctly) redirected to start page but without any notice that your session has expired and that you must login back
Now, I'm totally new with Seam, and I would expect the example application, which I'm using as some kind of staring point in developing my own application, to work flawlessly.
There are actually several more problems:
1. When you search for hotels, no matter what are the results, the links are always the same. The link is index-based instead of id-based, so it appears that you have already visited that/first hotel (purple vs. blue link) when in fact you haven't.
2. If you wait some time and you click the hotel link, you get an exception (I can't repeat this but it happened, parhaps after the conversation expired - I know I was going back and forth, waiting in some tabs and at some point I got an exception which could be traced into list not containing item number 2).
