Hi guys. i've just installed apache 4.0... what I wonder are: 1. is it a web server enabled with a servlet runner || (or) an application server? or what? 2. what is its advantage on using j2ee sdk provided by sun? it also obeys the j2ee specs. servlet jsp apis r available etc..
Tomcat is a servlet container. It receives the web requests and passes them to the Java web applications. Since JSP pages are turned into servlets behind the scenes and servlets are not stand-alone applications, they are loaded into memory by the container. So its safe to say that Tomcat is a "mini" application server. Hope this helps.
How does Tomcat differ from commercial products such as WebLogic or WebSphere? Are these all interchangeable for Servlet and JSP work?
WebSphere,Weblogic are containers for servlets,JSP's and EJB's. Tomcat is simply a container for Servlets and JSP's. The answer to your question is Yes. Any servlets/JSP's that you write should be usable in all three products. In fact if you are not doing EJB's in your project you may be better of using just a servlet container like Tomcat , Jetty or JRun.
Could someone explain this (simple to most I'm sure) and/or correct me? The only purpose of Apache is to accept HTTP requests, ability to set up virtual paths/home directories/etc.., for navigation, etc..,? So is Apache only good for setting up plain web sites (being HTML, PDFs, etc..,) or can it do anything other than that? I guess TomCat can do all that Apache web server does or do you also need to grab Apache web server when trying to create a web site? I was hoping for a simplistic explanation to how Apache and TomCat work, interact, and general tasks each perform. My understanding is that a JSP container, such as TomCat, allows communication with JSPs and so forth without having to compile programs each time before use, direct explicit passing of parameters, etc..,. Appreciate any feedback.
Indeed, Tomcat handles servlets and JSPs, which Apache by itself can't do. To this end, Apache needs to be set up to "forward" such requests to Tomcat, and after processing receive the results and send them back to the user. If all Apache did was just handle static pages like HTML and images, then Tomcat can do that as well. But Apache is much more flexible - you can configure lots more settings right out of the box, and there are tons of plug-in modules that extend its capabilities, e.g. you can set it up so that it handles PHP requests as well, or a number of other server-side languages. I would also assume that it scales much better, although I haven't seen a performance comparison in a long time.