Alexander Klimetschek wrote > I agree that an adaptTo(Class clazz, boolean doNotCache) seems a bit > "ugly", although it is definitely the caller that wants to make the > cache/no cache decision. > As a caller I don't want to care about implementation details - before we start adding such a mechanism we should rather skip the caching completly - though I really think we should keep caching in this area. Like we see with the input stream, it is up to the implementation providing the right behaviour - we could simply add support for implementations that don't want to cache their result as a general mechanism. But still it is then up to the implementation to decide.
Regards Carsten -- Carsten Ziegeler [email protected]
