This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I am relatively new to java web programming. I first learned how to do this on seam 2 with a seam-gen generated app. It's taken me awhile, but I finally realized that seam 3 is not exactly a shiny new version of seam 2, and that what I used to think of as my "seam app" is, in the next generation of j2ee, a "j2ee 6 app".
With that said, I have embarked on my first j2ee 6 app today. It's a new paradigm and I'm trying to figure it out.
One thing that is driving me nuts is that I keep getting a view expired error message! My app has one page, index.xhtml. It has an input field for a form. Every time I re-deploy I get the view expired exception and the most reliable way I've figured out how to get rid of it is to open a new tab. Obviously not the end of the world, but it's very annoying.
Why did this never happen with my seam 2 app, and how can I get it to stop in my j2ee 6 app! I sense that in the Brave New World I am relying on JSF for presentation which is historically a POST-oriented framework, and previously I relied on seam 2, which is a GET -oriented framework. Or something like that.
Based on other questions I've seen on forums, I sense this paradigm shift is confusing a lot of begining/intermediate level developers who first learned their trade on seam 2.
and my managed bean, or backing bean, or whatever the heck it is. It's a java class in any case :-)
I've got an Entity bean called Doors.java. I'm not going to post it because it doesn't contain anything interesting.
I'm deploying Jboss AS 7 if that matters.