Win a copy of Head First Go this week in the Go forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Liutauras Vilda
  • Bear Bibeault
  • Paul Clapham
  • Jeanne Boyarsky
  • Devaka Cooray
  • Junilu Lacar
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Ron McLeod
  • Tim Holloway
  • Claude Moore
  • Stephan van Hulst
  • Winston Gutkowski
  • Carey Brown
  • Frits Walraven

Reason behind not doing automatic compilation of Servlet like JSP equivalent Servlet  RSS feed

Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
When we run the JSP components JSP Container converts the JSP page in to equivalent Servlet and then Servlet Container compile and execute this servlet internally and displays the output on browser. But when we develop Servlet, before deploying/running on server we need to complile(if not developed on IDE) but Servlet container not complies this Servlet  automatically like above case(when we develop JSP) ?
Posts: 67243
IntelliJ IDE Java jQuery Mac Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Servlets are classes that, like all other Java classes, need to be compiled into class files before being used.

JSPs are markup templates that get automatically translated and compiled behind the scenes. The fact that JSPs are translated into servlets is an implementation detail that's specific to JSP. That this should somehow affect how servlets themselves work is a bit of an odd notion.
This will take every ounce of my mental strength! All for a tiny ad:
Become a Java guru with IntelliJ IDEA
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!