Re: [seam-dev] [cdi-dev] Stafeful services directly from the JSF VS "ViewBean" + stateless service

I tried this a few times recently. the main issue that pops up is that the EJB timeouts and WEB timeouts in the platform do not sync up. so if you're idle on a page for 5 minutes, your stateful EJB disappears, unless you have someone change container config. On Thu, Dec 22, 2011 at 5:49 AM, José Rodolfo Freitas <joserodolfo.freitas(a)gmail.com&gt; wrote: CDI created the possibility to reach any bean in the container from a JSF view, encouraging a closer approach between ejb and jsf (or any cdi bean and jsf), which can potentially lead to a simpler application design. I think that is great! However, I'm observing that this new programming model has been experimenting user resistance. The "traditional" way of doing things, using a "ViewBean" accessing a Stateless Service seems to be the more legit. What do you think about this? I'd like to discuss best practices around it as I see it's on the core of almost every web application design. _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev _______________________________________________ cdi-dev mailing list cdi-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/cdi-dev