I know it is a GWT group but as GWT uses embedded Jetty I hope someone with a deeper Jetty knowledge is reading my questions and willing to answer :)
We currently use Glassfish 3.1 with the following features: - EJB 3.1 Lite (only local no-interface beans, mainly for using @EJB) - @ManagedBean on some classes to be able to use @EJB inside - JPA 2.x (Eclipselink) - JAX-RS 1.1 - Servlet 3.0 - Session Failover / Clustering - Connection pooling and validation - maybe in the future: web sockets / push Our server code is pretty stateless and with some rewrite I guess we could get rid of @ManagedBean classes and maybe also of EJBs as we only use them for easy @EJB injection (could be done with google guice also). Is it possible to integrate these features into Jetty? Do you think this will result in some performance increase (and memory reduce)? Does anyone use GWT + Jetty in production or even has compared Jetty + J2EE features with Glassfish? If its possible to integrate all of these features, how robust is session failover / clustering? Could we also configure the embedded jetty used by GWT Eclipse Plugin to match our production settings (J2EE features + same application context root + hot redeploy)? Thanks in advance. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
