Closed GoogleCodeExporter closed 9 years ago
I don't think that we should modify behavior of Cacheable annotation because
it's not a part of SSM but Spring. If you want such feature you should request
it from Spring team then SSM will support it out of the box.
In raw SSM there is a workaround. You can use SerializationType.CUSTOM and
register custom cache transcoder using CacheFactory. In the transcoder you can
define how to serialize and deserialize objects of given type.
Original comment by ragno...@gmail.com
on 23 Jan 2014 at 1:12
Thank you so much. This is exactly what I need :)
Original comment by cemalettin.koc@gmail.com
on 23 Jan 2014 at 2:04
Great! I'll close the issue. If you find any issues with the
SerializationType.CUSTOM please let me know and open another issue.
Original comment by ragno...@gmail.com
on 24 Jan 2014 at 9:11
Original issue reported on code.google.com by
cemalettin.koc@gmail.com
on 23 Jan 2014 at 9:37