cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vadim Gritsenko" <>
Subject RE: Unexpected behavior with imported stylesheets
Date Mon, 01 Jul 2002 17:43:41 GMT
> From: Jason Uithol []
> Hello,
> Shoot me if I'm wrong.

Gimme a gun...

> This is to do with the Source (?) class isn't it ?  It has a
> lastModified(...) function.  Source is created for the "importing"
> stylesheet, and lastModified of course returns the last modified of
> "importing" file. 

This is right.

> It would have to open the file, *parse* it and
> recursively traverse through it's import and include tags to find the
> "imported" files ( and their "imported" files :) opening and parsing
> them as well, get _their_ last modifieds and keep track of the most
> one out of that lot.

And this is not. For files, there is File.getLastModified (or similar),
and for URLs... there is something similar too
(connection.getLastModified()). If modification time is not known,
result of transformation (and stylesheet itself) is not cached.

> It is a pain to touch every single xsl that imports another one, but
> above approach, if implemented in the "raw" way described above, would
> a lot of thrashing around !

Don't know what you mean under "raw"... But it is implemented for a
couple of weeks by now (or more).

> I suppose this a better question for the dev list, but would their be
> easy way to monitor a list of files for their last modifieds ? 

There is an idea to use async process to monitor all files... May be it
will be implemented some day, when this start affecting performance.
Right now, this checking is far from bottleneck.

PS You owe me a gun ;)


> ( Like JBoss
> does )  That might make a better solution available.
> Jason.

Please check that your question  has not already been answered in the
FAQ before posting.     <>

To unsubscribe, e-mail:     <>
For additional commands, e-mail:   <>

View raw message