after one day of coupling with two problems in my Seam 2.2.0.GA application I decided to give Seam 2.1.1.GA a try. After downgrading the problems are gone.
Since the application code is the same I think there are two possible causes for those problems. Whether I didn't proper migrate to Seam 2.2.0.GA or there are some bugs.
The first problem regards the manual flush mode for Hibernate. I have some Seam components which start a long running conversation with a manual flush mode. The problem here is, that the entity manager still is in auto mode. Therefore all the changes are reflected in the database and that's not very good. I use a SMPC and inject the entity manager with @In.
The other problem has also something to do with conversations. I use a menu from ICEfaces to enable the user to navigate around in the application. Every menu entry reflects one use case. In the pages.xml I said that every navigation action should end the current conversation (before-redirect=true) and redirect to the chosen page. This way there is always only one active conversation for each user at all (except the user thinks about using tabs).
The problem here is, that there is one page that doesn't end the conversation before redirecting. This means that every time the user visits this page there is one additional conversation started.
Those problems are strange. They are even more strange regarding the fact that a downgrade to Seam 2.1.1.GA solves them.
Has somebody an idea if there are known issues or are there common mistakes a developer like me provokes such problems?