commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Grobmeier <>
Subject Re: [OGNL] CacheException
Date Wed, 01 Feb 2012 16:03:51 GMT
On Wed, Feb 1, 2012 at 4:55 PM, Maurizio Cucchiara
<> wrote:
> Hi guys,
> I was trying to integrate Struts2 with the new api layout.
> Unfortunately I realized that due to the introduction of the new checked
> CacheException [1] (which basically inherits the Exception class), every
> method (which uses a cache, practically all of them) of OgnlRuntime [2]
> must throw the aforementioned exception.
> Furthermore it seems that there is only one class able to produce
> exceptions [3]
> This is make very hard the integration process of Struts2.
> I was thinking to change the exception in a unchecked version, but [3]
> makes me think the contrary.

Why do you now think contrary?

When I read the first part of your message I thought: heck, why is it
a checked exception?
Stupid question: can a OgnlException exception occur on objects in the
cache? I mean in practice...
To my understanding the checked OgnlException occurs before putting
something into the cache. 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


> I would like to know your thought.
> [1]
> [2]
> [3]
> Twitter     :
> G+          :
> Linkedin    :
> Maurizio Cucchiara


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message