aspose file tools
The moose likes Web Component Certification (SCWCD/OCPJWCD) and the fly likes Jsp doubt Big Moose Saloon
  Search | Java FAQ | Recent Topics
Register / Login
JavaRanch » Java Forums » Certification » Web Component Certification (SCWCD/OCPJWCD)
Reply Bookmark "Jsp doubt" Watch "Jsp doubt" New topic
Author

Jsp doubt

Marcos Urata
Greenhorn

Joined: Dec 31, 2004
Posts: 26
If a jsp becomes a servlet, and everytime you (the developer) change your jsp code a new servlet representing that .jsp will be created (replacing an existing one), how come it is not necessary to restart the container??
Colin Fletcher
Ranch Hand

Joined: Sep 10, 2004
Posts: 200
I would be necessary to re-deploy the application. This could be accomplished by copying the war file to the webapp folder and 'telling the container to restart the webapp' or restarting the container.


SCJP 1.4 SCWCD 1.4
Marcos Urata
Greenhorn

Joined: Dec 31, 2004
Posts: 26
No! It is not necessary (At least with tomcat)! That�s the point of my question. Why it is not necessary to redeploy the application (or just the *.jsp that were altered) if they will become a servlet??

Try it out!!
Saket Barve
Ranch Hand

Joined: Dec 19, 2002
Posts: 224
Marcos,

The container will look if there have been any changes in the JSP file being called. If such is indeed the case, the JSP page will be compiled all over again to form a new servlet and so on.

In my experience, Tomcat does not always take the latest JSP files so sooner or later, you'll perhaps want to restart anyway when making crucial changes. Often times I also delete the contents of work and logs directories to ascertain the needful.

Regards,
Saket
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Jsp doubt
 
Similar Threads
attributes and listener hfsj question 10
Do you have elegant way of nullpointer exceptions
Scriptlets -> Time and Space Complexity
difference
is servlet and jsp same?