...
Thanks for the feedback, your confirming my thoughts, but what strikes me is that the given class ExpiresValidity has been removed explicitly from the repository, and it doesn't seem as if it was to move it to some other place, please correct me if I'm wrong.
No, it just moved to the excalibur sourceresolve project which is included as a binary jar in Cocoon (look for excalibur-sourceresolve-YYYYMMDD.jar). There are a number of internal pieces of Cocoon that are imported from other projects because they have general usefulness outside of Cocoon. In many cases, the same Cocoon developers are involved in those projects as well.
One such reason, of course, would be if there was some other more "right" way of achieving that caching purpose by the mean for example of some dedicated transformer or action. Please again, I would be grateful if you could tell me if it is so.
No, this is the right way. No dedicated transformer or action is necessary. The pipeline handles the actual caching.
I also tried an alternative: my XSP page is basically an esql page, so I tried to fill my need by using the SQLTransformer which I hadn't tried before. I managed to get it working, it's pretty straightforward, but it doesn't seem possible to specify the validity, so basically, I'm stuck with the same problem as before. And this leads to the discussion led in thread: http://marc.theaimsgroup.com/?t=106055805900001&r=1&w=2 I look forward seeing the solution of that issue.
AFAIK the SQLTransformer is not yet cacheable. For now, stick with esql using the code I provided before. It will work. If it doesn't write back and tell us what went wrong.
Geoff
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
