[COCOON-1279] caching point pipelines and smart caching

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.1.5
• Fix Version/s: 2.1.9, 2.2
• Component/s: - Components: Avalon
• Environment: Operating System: Linux; Platform: PC
• Bugzilla Id: 31432
• Assignee: Jean-Baptiste Quenot
• Reporter: Oliver Powell
• Created: 27/Sep/04 12:34
• Updated: 03/Oct/06 09:50
• Resolved: 03/Oct/06 09:50

Description

I think if you choose to use caching-point type caching, then smart-caching
should effectively be automatically turned off. Or, in other words, I would
expect when using the caching-point pipeline processor that it would by default
behave as it does when smart-caching is off: which is to always look for shorter
keys in the cache if a response is not found for the current key combination.

Perhaps this could be implemented by having CachingPointProcessingPipeline
override the validatePipeline method to make it always try shorter keys (at the
same time, remove this functionality from the AbstractCachingProcessingPipeline).