The cache implementation to use is up to the user of the feature. All that is needed is an implementation of ICacheProvider, for our needs we use EhCache.
The header Pragma: no-cache is a very good idea, and would be very easy to implement. The default key generator is built by our own needs. We have data in the body that we need to include in the cache key, and our bodies are always very small so I guess that's not a problem for us but could be problematic when the messages are bigger. Even the key generator is overridable via ICacheKeyGenerator interface if the body isn't desirable. One could even extend the default implementation and add properties for how the key should be generated. The @Cachable annotation is used to mark those methods that should be cached, no matter what the HTTP action is. Thanks for the reply. -- View this message in context: http://cxf.547215.n5.nabble.com/Show-Cxf-caching-tp5738377p5738414.html Sent from the cxf-user mailing list archive at Nabble.com.
