Howard W. Smith, Jr. wrote >> ViewExpiredExceptions are 'no' longer a concern of mine since I am using >> OmniFaces restoreView component. > > Nice! I hadn't seen that. I will be checking that out. > >> Also, for my home-grown/custom security-n-session-management >> implementation, my login page access @SessionScoped userBean.login, but >> since I've been hearing others advise to use @RequestScoped more than >> @SessionScoped (as much as possible), I am considering changing my >> implementation, so the login page will access @RequestScoped user bean >> instead of @SessionScoped. I am quite sure that that will allow my login >> page to sufficiently/theoretically avoid View Expired exception. I plan >> to >> try this...when I feel like it, or have bandwidth to do so. :) > > Nope :( View state is still maintained even when only referencing > RequestScoped beans. That is why the transient=true is so important. It > will be the only standard built in way to avoid view state exceptions that > I know of.
-- View this message in context: http://myfaces.10567.n7.nabble.com/Add-Stateless-JSF-to-MyFaces-Core-Is-it-really-necessary-tp114248p115116.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
