The only case is, as I said before, the [3] (take a look at lines 71-78). In this case two checked exceptions are encapsulated in a CacheException. But I think that we can live with them, maybe we will come back later.
So if there are no objection, I would change the hierarchy of CacheException to a RuntimeException (with this change the integration is practically insignificant, apart from the package name) [3] http://svn.apache.org/viewvc/commons/proper/ognl/trunk/src/main/java/org/apache/commons/ognl/internal/entry/PropertyDescriptorCacheEntryFactory.java?revision=1194960&view=markup Twitter :http://www.twitter.com/m_cucchiara G+ :https://plus.google.com/107903711540963855921 Linkedin :http://www.linkedin.com/in/mauriziocucchiara Maurizio Cucchiara On 1 February 2012 17:03, Christian Grobmeier <[email protected]> wrote: > Therefore the CachedException is more or > less an exception which is somehow produced at runtime, due to a > programming error. Sounds like a runtime exception for me, but I > would love to hear why you are not thinking different >
