We are using JBoss 4.2.0 with Seam.
Currently we meet a long running conversation problem just after upgrading seam from 2.0.0 Beta1 to 2.0.0 GA. The problem is described as following.
We have a scenario of long running conversation involving three stateful beans, Bean A (@Begin init()), Bean B (@Begin(join=true) init() ), Bean C (@Begin(join=true) init() ). These three beans are backing three pages (Page A, Page B, and Page C) individually.
Page A invokes the Bean AÃ¢Â€Â™s init( ) method to start the long conversation; When user inputs some data and clicks a Ã¢Â€ÂœGoÃ¢Â€Â� button on Page A, the user is navigated to Page B and Bean B joins the conversation by its init() method invoked; Then after user inputs some data and clicks a Ã¢Â€ÂœGoÃ¢Â€Â� button on Page B, the user is navigated to Page C and Bean C joins the conversation by its init() method invoked.
So far so good. But the problem comes when user clicks Ã¢Â€ÂœDoneÃ¢Â€Â� button on Page C and the user is navigated back to Page B. At this time, it is observed that the states of Bean B are not restored (lost). (The Beam B object reference is retrieved correctly)
Previously with Seam 2.0.0 Beta1, it was observed that the states of Bean B were restored correctly.
Is there anyone who met the same problem? Can Seam team give some clue to solve the problem or workaround?
You're going to need to post actual code, I have no idea what you are trying do say.