Yes, this is reasonable. When my head clears, will take a look and get
this in.
geir
David Rees wrote:
>
> > -----Original Message-----
> > From: Andreas Wikberger [mailto:[EMAIL PROTECTED]]
> >
> > Hello,
> >
> > I have encountered a probable bug/problem with the caching of templates in
> > Velocity. The effect of the bug is that I have to request a page two times
> > after I have made a change to a template before the changes
> > get visible and Velocity uses the changes I made in the template.
> >
> > After checking my own TemplateLoader for errors and not finding any
> > there (i think :)) I checked the source code to find out what
> > really happend.
> > And what I found was that in the method requiresChecking() of the Resource
> > class a check is made wheater to check for changes in a specific template.
>
> You know, the exact same bug has been bugging me for a while, too. I looked
> at the source code briefly and didn't see anything wrong, but now I see that
> your analysis and fix is correct.
>
> Geir, can get get this patch in the next release? It would save me from
> hitting reload twice during development. (I like to keep a 2s cache
> interval even on development machines).
>
> -Dave
--
Geir Magnusson Jr. [EMAIL PROTECTED]
System and Software Consulting
Developing for the web? See http://jakarta.apache.org/velocity/
Be well, do good work, and keep in touch.
