Win a copy of Escape Velocity: Better Metrics for Agile Teams this week in the Agile and Other Processes 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Tim Cooke
  • Paul Clapham
  • Jeanne Boyarsky
Sheriffs:
  • Ron McLeod
  • Frank Carver
  • Junilu Lacar
Saloon Keepers:
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
Bartenders:
  • Piet Souris
  • Frits Walraven
  • fred rosenberger

Modified Jsp

 
Ranch Hand
Posts: 70
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi all,
It is understood that the container checks the last modified timestamp for a jsp page and then loads it. Which means, if i modify a jsp today, which was written and tested yesterday, the container will check for the lastmodifiedDate and recompile the jsp to give new output.
This works fine.

Suppose i back date the system date and change the jsp, the new output is not shown..
Does this mean, that the web container only checks for the timestamp and has no other way of knowing that a jsp page has been modified??

is it then not a danger that my new jsp pages will not come into effect, in case i back date my system..???

How does the container handle this?

Any inputs will be highly appreciated.

Thanx in advance,
Chhaya
 
Ranch Hand
Posts: 121
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Chay,
The container is least bothered about timestamps.From my understanding every JSP page is compiled whenever it is changed. The timestamp of the JSP hardly matters.It is the containers problem, it compares the jsp with the already compiled servlet to check for differences whenever it is turned on. Probably the first hit takes time for the very same reason that it gets recompiled.
Shoot if u have any more questions.
 
author
Posts: 3252
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Whether JSPs get recompiled, and indeed how the container detects the change, is container specific. Having said that, none of the containers I'm familiar with actually compare the JSP contents; they simply detect changes in the last modified time.

- Peter
 
Sheriff
Posts: 67671
173
Mac Mac OS X IntelliJ IDE jQuery TypeScript Java iOS
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Ummm, what Peter said.

Additionally, if you "lie" to the container by changing system times on it, you can't really expect reasonable behavior, can you?

Deepak, what containers do you know of that actually compare contents? Or are you speaking out of your hat?
[ June 07, 2004: Message edited by: Bear Bibeault ]
 
Anything worth doing well is worth doing poorly first. Just look at this tiny ad:
the value of filler advertising in 2021
https://coderanch.com/t/730886/filler-advertising
reply
    Bookmark Topic Watch Topic
  • New Topic