hi toto, 1. if you use NOPValidity avoid garbage creation by using the shared singleton instance (NOPValidity.SHARED_INSTANCE IIRC) 2. you seem to misunderstand how SourceValidity's are supposed to work. Validity here should probably better be called Validator, since SourceValidity's responsibility is to function as cache (entry) validator. anyway, you are performing that 'is the entry valid?' in your getValidity() method by checking an external condition, so that's wrong (design-wise); move that logic into the validator/SourceValidity. this might require a custom SourceValidity, of course.
> -----Ursprungliche Nachricht----- > Von: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Auftrag > von toto > Gesendet: Mittwoch, 3. Marz 2004 20:38 > An: [EMAIL PROTECTED] > Betreff: caching - getValidity() > > > Hi, > > i'm having trouble with the getValidity() method. > i'd like to invalidate the cached response under certain condition : > > public SourceValidity getValidity() { > if (externalCondition) { > return null; > } else { > return new NOPValidity(); > } > } > > however, once NOPValidity is returned, the validity of the > cached response > is never checked again (unless the new and the cached keys differ). So, > how > can i have the validiy checked everytime the component is used? > > thnx in advance > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
