On 5/29/07, Dave Newton <[EMAIL PROTECTED]> wrote:
I'm starting to feel like we're doing your homework for you.
I'm sorry you feel that way. If you prefer not to reply, its your prerogative. I am just trying to understand the technology.
A "Struts project" is not a servlet. A Struts project might *have* a servlet (and in S1 is pretty much guaranteed to have at least one), but in S2 they might be considered an anomaly.
"JSPs are compiled into Java Servlets by a JSP compiler. [1]" The way I see it, so long as the result is a JSP page, the project contains a servlet. Granted, one can easily write the viewer component without JSP, but I think its fair to guess that a large percentage of Struts projects make use of JSP pages.
A web application is any application that runs on the web, like a blog, or web email, or social site, or whatever.
A blog, web mail or social site that was written in Java and runs on or inside a standard server such as Tomcat would be a servlet, though. As far as I can tell, it meets all the requirements. It sounds like, for any program (end point; excluding containers, such as Tomcat, Struts, etc) accessed via a browser, if it is written in Java, it is a servlet, otherwise its a web application. How about a solid clear definition of a servlet? [1] http://en.wikipedia.org/wiki/JavaServer_Pages --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
