I have a managed bean in the request scope that I'm using in a form screen. I tend to favor the request scope as it reduces all the trouble with the back button, reload, etc.
When clicking "edit" on an existing object, I get the data from the database, and stuff it into the request map. The navigation case goes to the edit screen. I don't have "redirect" set, and the url in the browser stays the same, so I assume it isn't redirecting. Yet, the data doesn't get into the form.
If I put the object in the session map, it shows up in the form.
I also tried checking the managed bean right after I set it in the request map by calling...
app.createValueBinding("#{"+ key +"}").getValue(facesContext);
Running this in the debugger (with the correct key) returns the object I set.
So, somewhere in there its dropping my object. Does it consider this a new request, even though it hasn't left the server? I guess I should try a scriptlet in the
jsp page next, just to see if the object is available by the time it gets there.
While I'm on the subject, one of the biggest issues I've always had with
jsf is the session and server storage of the view. Seems like we've given up on back button support, but I'm not sure users have. Any thoughts on that?