Chris, On Fri, Feb 1, 2013 at 2:20 PM, Christopher Schultz <ch...@christopherschultz.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Howard, > > On 2/1/13 12:41 PM, Howard W. Smith, Jr. wrote: >> my app is running fine, but i'm always striving for perfection and >> performance, and that is why I made my way from mojarra to >> myfaces, glassfish to tomee/tomcat, and jsf-managed-beans to >> cdi-managed-beans, and just early this morning from APR to NIO >> connector. > > If you want to improve performance even more, ditch EJB altogether.
Wow, that hurt. ditch EJB altogether? I 'grew up' on EJB. When I was migrating from JSF managed beans to CDI managed beans, I recognized that I could reference EJBs via @Inject or @EJB via TomEE/OpenWebBeans, but I stuck with @EJB...'just because'. when I first read your recommendation, earlier on, i thought to myself, okay, that should be easy, but now, I don't know how I would 'ditch EJB altogether'. All of my EJBs are accessing database via JPA; there are a few native SQL statements, lot of dynamic SQL statements that I redefined as named queries. If you are referring to CDI managed beans performing database access... I think I read one blog that stated that CDI can do anything that EJB can do, but still, I guess I have not seen any examples where CDI bean is accessing database. So, why do you recommend to 'ditch EJB altogether'... to improve performance? please explain. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
