I have nothing against Jetty, but honestly, for most users there is not a terribly significant difference in performance or ease of use between Jetty and Tomcat. Those who tell you that changing from Jetty to Tomcat to any other container out there will make a significant impact on your development time are selling false hope. The startup time of both containers is usually insignificantly small compared to the startup and initialization time of your application classes. My tomcat container takes 1 second to startup on my computer. So even if Jetty were twice as fast, I would have gained half a second, the rest of my application takes 9 seconds to startup so you can see that changing containers won't help me much.
Now I am focusing just on startup time. From looking through the docs, it doesn't seem like Jetty is any more magical in class loading such that it would require less restarts than with tomcat. I'm not an expert so if someone has information regarding Jetty and class loading I'd be interested in hearing it. I actually use both containers. I use Tomcat in eclipse because it integrates extremely easily with WTP. I use Jetty to run from the command-line because of it's dead-simple integration with maven. I really can't tell any difference between them. They both seem to run just as fast and startup just as quickly. If there's any difference at all it is probably noticeable under a heavier load and not really during development. On 2/15/07, Murray Collingwood <[EMAIL PROTECTED]> wrote:
Hi all Does anybody else find this hellishly confusing? It makes me want to throw everything out and go back to a nice simple DOS system and a Turbo C compiler! How much simpler it was back then... Okay, I downloaded the latest Eclipse system, copied my project into a fresh workspace. Saving a file was back to a sub-second response. Actually I tried saving a second file to make sure it wasn't a fluke the first time. There was definitely a problem somewhere and it has now gone away. Okay, now the second part of the problem. Tomcat or Jetty??? I don't want to package every time I make a small change to a config file or HTML, so I want the servlet engine to use my files from my development area. My previous frustrations with restarting tomcat have encouraged me down the Jetty track - I downloaded Jetty 6 yesterday and the test system was working in about 5 minutes, pretty good. I then added a context.xml for my application and now when I start Jetty it simple crashes and refuses to start the application. I get an error like: 'No class for Servlet or Filter' I haven't been able to find any help on this error. I did find information on a Jetty-Maven-Plugin but form my reading this is all about packaging the application - I don't want to go there. I also found a number of recent comments about Maven2 saying it was still quite buggy. Do I press ahead trying to solve the Jetty stuff or do I revert back to a Tomcat system....??? I'm developing in a Windows XP environment so this may limit me from some of the options suggested here. PS Thanks to everybody who has contributed so far - I really appreciate your ideas and suggestions. You really are a very friendly bunch of people. PPS My computer is an Intel 2.8ghz processor with 1gb ram and 80gb harddrive. It's not slow with other stuff. Cheers Murray Some of my understandings: Sysdeo-tomcat-plugin - packages app and restarts Tomcat WTP - packages app and restarts Tomcat Web Standard Tools - I was using this AJDT - never used it Jetty6 plugin - is this the Jetty-maven-plugin referred above of different? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
