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.<br>
<br><div class="gmail_quote">On Thu, Dec 22, 2011 at 5:49 AM, José Rodolfo Freitas <span dir="ltr"><<a href="mailto:joserodolfo.freitas@gmail.com">joserodolfo.freitas@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
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!<div>
<br></div><div>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 </div>
<div>more legit.</div><div><br></div><div>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. </div><div><br></div><div><br>
</div><div><br></div><div><div><br></div></div>
<br>_______________________________________________<br>
seam-dev mailing list<br>
<a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
<br></blockquote></div><br>