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
Hi Izio,
the benefit of having OGNL at commons is IMHO serving all the ASF
projects that used it in a better way, so feel free to change the APIs
according to Struts' need!!! :)
All the best,
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/
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 us
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 th