* Carsten Ziegeler: > Imho as this is a bug, I think it doesn't make sense > to keep compatibility. I will update the status file > accordingly. Now if you want to have compatibility we could > keep the old implementation using a different class name > (DeprecatedCachingCoplet or something like that).
As long as we can manage to find a code snippet to invalidate a CachingURICoplet, there is no need to maintain compatibility. We will update our application accordingly. Thanks for your help, -- Jean-Baptiste Quenot Systèmes d'Information ANYWARE TECHNOLOGIES Tel : +33 (0)5 61 00 52 90 Fax : +33 (0)5 61 00 51 46 http://www.anyware-tech.com/
