On Fri, May 29, 2009 at 1:36 AM, Ian Michell <ianmichell(a)gmail.com&gt; wrote: Yes, I did research into this setting and my conclusion was that you should not use it because it breaks things horribly. It's not just the pageflow it breaks. You get into hot water in other areas too (I'm not recalling exactly at the moment what it is). The approach in JSF 2 is much better and was designed for this setting, so basically don't use it in Facelets (the non-JSF 2 version). -Dan -- Dan Allen Senior Software Engineer, Red Hat | Author of Seam in Action http://mojavelinux.com http://mojavelinux.com/seaminaction http://in.relation.to/Bloggers/Dan NOTE: While I make a strong effort to keep up with my email on a daily basis, personal or other work matters can sometimes keep me away from my email. If you contact me, but don't hear back for more than a week, it is very likely that I am excessively backlogged or the message was caught in the spam filters. Please don't hesitate to resend a message if you feel that it did not reach my attention.

On Sat, May 30, 2009 at 12:36 AM, Ian Michell <ianmichell(a)gmail.com&gt; wrote: So are you saying you are having a problem with the Seam feature when using the regular approach or just when using the build-before-restore. The problem with build-before-restore is that it is just broken in Facelets. I wish I remembered the exact details, but I can say that it needed to be reworked quite a lot before it became the standard approach in JSF 2.0. -Dan -- Dan Allen Senior Software Engineer, Red Hat | Author of Seam in Action http://mojavelinux.com http://mojavelinux.com/seaminaction http://in.relation.to/Bloggers/Dan NOTE: While I make a strong effort to keep up with my email on a daily basis, personal or other work matters can sometimes keep me away from my email. If you contact me, but don't hear back for more than a week, it is very likely that I am excessively backlogged or the message was caught in the spam filters. Please don't hesitate to resend a message if you feel that it did not reach my attention.

So you are trying to work around the "user sits on the login page for too long and it times out". There are two alternative ways to work around this problem without BUILD_BEFORE_RESTORE. #1. You can put a timer on the login page to automatically refresh itself after a fixed about of time so that the user always has a fresh page. You can simply use a meta tag for this or you can get fancy and do JavaScript. #2. You can use a plain form rather than a JSF form and then process the login using a page action. You can still submit via post, but it will be treated like an initial request. The username and password will be available for injection using @RequestParameter or bound to an object using page parameters. Give either of those a try and see how it works out for you. Perhaps we can get those suggestions in the knowledgebase. I'm hoping the transition to Seam 3.0 and JSF 2.0 will be as painless as It's going to be a while before we can even begin to talk about migration. Folks getting involved with Seam 3 now should understand that they are coding for something that is "next generation". While there will be a smooth way to use Seam 2 components, the very nature of Seam 3 changes rather significantly because JSR-299 is a quite a stark change in mindset. But it's really too early to make any statement about what the path will look like...you can certainly have input in what it will be, though. -Dan -- Dan Allen Senior Software Engineer, Red Hat | Author of Seam in Action http://mojavelinux.com http://mojavelinux.com/seaminaction http://in.relation.to/Bloggers/Dan NOTE: While I make a strong effort to keep up with my email on a daily basis, personal or other work matters can sometimes keep me away from my email. If you contact me, but don't hear back for more than a week, it is very likely that I am excessively backlogged or the message was caught in the spam filters. Please don't hesitate to resend a message if you feel that it did not reach my attention.

Ian, I had the same issue. What I ended up doing was creating/registering a custom Seam ExceptionHandler to catch ViewExpiredExceptions and redirecting to the page. The good thing is that the ViewExpiredException contains the View Id of the view that the user was trying to access, so you can just do a GET redirect to the page. The user will loose their inputed data, but at least the page will render correctly. Drew Kutcharian Chief Technology Officer Venarc Inc. www.venarc.com Phone: 818-524-2500 ----- Original Message ----- From: "Ian Michell" <ianmichell(a)gmail.com&gt; To: "Dan Allen" <dan.j.allen(a)gmail.com&gt; Cc: seam-dev(a)lists.jboss.org Sent: Friday, May 29, 2009 9:36:39 PM GMT -08:00 US/Canada Pacific Subject: Re: [seam-dev] build before restore Yeah, I guess I will have to write a work around for now, as a redirect with a message doesn't work either (although the pages.xml schema says it does), so once you log out and try to do a form post, seam throws the view state exception, however if you logout and then do a redirect it works fine, apart from the fact that I lose the message I pass on successful logout -- Almost as frustrating as seam mail! Ian On 29 May 2009, at 20:25, Dan Allen wrote: On Fri, May 29, 2009 at 1:36 AM, Ian Michell < ianmichell(a)gmail.com > wrote: Hi All, I'm new to the list... Hash anyone noticed that the facelet parameter BUILD_BEFORE_RESTORE breaks pageflow (as in, using a normal JSF form refuses to continue run the pageflow)? Once the parameter is removed from the web xml pageflow starts working again. Yes, I did research into this setting and my conclusion was that you should not use it because it breaks things horribly. It's not just the pageflow it breaks. You get into hot water in other areas too (I'm not recalling exactly at the moment what it is). The approach in JSF 2 is much better and was designed for this setting, so basically don't use it in Facelets (the non-JSF 2 version). -Dan -- Dan Allen Senior Software Engineer, Red Hat | Author of Seam in Action http://mojavelinux.com http://mojavelinux.com/seaminaction http://in.relation.to/Bloggers/Dan NOTE: While I make a strong effort to keep up with my email on a daily basis, personal or other work matters can sometimes keep me away from my email. If you contact me, but don't hear back for more than a week, it is very likely that I am excessively backlogged or the message was caught in the spam filters. Please don't hesitate to resend a message if you feel that it did not reach my attention. _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

http://seamframework.org/Documentation/UsersAreSeeingAViewExpiredExceptio... On Fri, Jun 12, 2009 at 7:54 PM, Dan Allen <dan.j.allen(a)gmail.com&gt; wrote: -- Dan Allen Senior Software Engineer, Red Hat | Author of Seam in Action http://mojavelinux.com http://mojavelinux.com/seaminaction http://in.relation.to/Bloggers/Dan NOTE: While I make a strong effort to keep up with my email on a daily basis, personal or other work matters can sometimes keep me away from my email. If you contact me, but don't hear back for more than a week, it is very likely that I am excessively backlogged or the message was caught in the spam filters. Please don't hesitate to resend a message if you feel that it did not reach my attention.