From: Jim A. <ji...@ar...> - 2001-04-23 21:12:31
|
Actually, I tried Jetty (as part of the jBoss 2.2.1 bundle) just the other day. It installed fine but when I deployed my EAR I got a bunch of errors complaining about JNDI. When I ran my app, I got a bunch of maning exceptions. I have not had time to look into this further, but it did make me wonder if Jetty is fully intergrated, like Tomcat is. I would have expected the very same EAR to run just the same under either Jetty or Tomcat... Jim --On Friday, April 20, 2001 1:50 AM -0500 danch <da...@nv...> wrote: > Alternatively, Tomcat is the reference implementation. Jetty is > lightweight and fast. > > The only other thing is that (judging from traffic analysis of these > mailing lists) Integration of Tomcat with JBoss is better tested. (Jetty > users, feel free to argue) > > -danch > > Alvin Yap wrote: > >> Tomcat is more robust and extensible. Jetty is lightweight and fast. >> >> Alvin >> >> Jason Dillon wrote: >> >> >>> Does anyone have any opinions as to which contain is more robust, >>> easier to use and such? >>> >>> --jason >>> >>> _______________________________________________ >>> JBoss-user mailing list >>> JBo...@li... >>> http://lists.sourceforge.net/lists/listinfo/jboss-user >> >> >> >> _______________________________________________ >> JBoss-user mailing list >> JBo...@li... >> http://lists.sourceforge.net/lists/listinfo/jboss-user > > > > _______________________________________________ > JBoss-user mailing list > JBo...@li... > http://lists.sourceforge.net/lists/listinfo/jboss-user ******************************************** I shall be telling this with a sigh Somewhere ages and ages hence: Two roads diverged in a wood, and I - I took the one less traveled by, And that has made all the difference. - Robert Frost, 1916 |