Are you sure you're not getting a new session each time (blocking cookies, or whatnot)? Just for kicks, what happens if you change your JavaBean to a SFSB?
Oh, and there may or may not be a problem with the server side state saving in the facelets version that ships with Seam 1.0.1.
<context-param> <param-name>javax.faces.STATE_SAVING_METHOD</param-name> <param-value>client</param-value> </context-param>
to web.xml and see if that helps. If so, DL the latest facelets.jar from https://facelets.dev.java.net/ and use that instead.
Thanks for the response.
I tried your suggestions and got the same results after making my bean a SFSB!
By the way, I am using client side state saving, facelets 1.1.11, and Seam 1.0.1 on Tomcat 5.5.17 with embedded EJB3.0 container.
...and cookies are enabled.
How are you creating your component? Do you have a managed-bean of the same name configured in faces-config.xml?
Not at this time. It was initially registered only in faces-config. Then I tried @Name then SFSB. Finally, I got rid of the bean alltogether. I was beginning to have suspicions that the problem had something to do with the tomahawk tabbed pane tag and its binding to one of the bean's properties. Unfortunately, time constraints have forced me to find an alternative solution: I am no longer using the tomahawk tabbed pane and its backing bean.
Thanks for all your help.