I hear that integration with Jetty works somewhat better due to the developers actively participating in the JBoss integration effort. Also it seems Jetty is currently a bit faster as well.
Sorry for the stupid question, but I assume JBossWeb == Jetty?
Can anybody be more specific on this? I guess many of us think often about if we have made the right decision on choosing Jetty or Tomcat. Is Jetty that faster so that it is worth not to use Tomcat? Which Apache connector is faster, Jettty or Tomcat? Are there any other advantages/disadvantages on any of them? Which of them do JBoss Gurus prefer...
Thanks for any info. Until then, I'll keep on with Tomcat as I use it for projects that don't need J2EE.
Personally I think it makes little difference which one you go with. Jboss uses it by default so that should tell you which one they prefer.
If in doubt go jetty as this seems to be sticking pretty close to jboss these days.
>Any input would be greatly appreciated.
The quick start guide chap 13 states the jboss-jetty integration.
On of them is about optimized calls:
In-JVM optimized calls.
The overhead of RMI is avoided when the servlet and EJB containers are run in the same JVM.
I think this implies tomcat-jboss calls take the overhead of RMI.
tomcat-jboss is in the same jvm and so does not have the overhead.
Jetty as mentioned above though is and will be probably better integrated as jboss continues to develop.
The Jetty community is amazingly responsive and its lead developers offer excellent support. We find Jetty is very flexible an integrated web container, and particularly when used stand-alone on a separate web server tier in conjunction with Jboss.
> tomcat-jboss is in the same jvm and so does not have the overhead.
It surely true for local interfaces to ejb.
But is it also true for remote interfaces?
I thought jetty integration was optimized for remote access but tomcat wasn't because I've ever read some document about this in earlier JBoss release (may be , with JBoss 2.x).
Sorry I'm a little confusing about web container and jboss integration for version 3.x.
Please correct me if I'm wrong.
Tomcat is also optimized for in-VM calls even when using remote interfaces as long as both Tomcat and JBoss are running inside the same VM (although this optimization was off by default in 2.4.x series IIRC).
(the pass-by-ref check is in the remote proxy implementation)