Integration of ssm with mvc spring application throws exception with jackson 1.7.1 about simple-spring-memcached

[GoogleCodeExporter]

Thanks for creating the issue

Original comment by [email protected] on 5 Dec 2012 at 9:50

• Changed state: Started

[GoogleCodeExporter]

Added initializeTranscoders property to CacheFactory by default set to true. If 
set false transcoders won't be created automatically (including json 
transcoder) so jackson classes (ObjectMapper) won't be initialized.
Code in trunk.

Original comment by [email protected] on 26 Mar 2013 at 8:45

• Changed state: Ready

[GoogleCodeExporter]

Original comment by [email protected] on 24 Jun 2013 at 8:27

• Added labels: Milestone-Release3.2.0

[GoogleCodeExporter]

Included in release 3.2.0

Original comment by [email protected] on 27 Jun 2013 at 7:58

• Changed state: Fixed

[GoogleCodeExporter]

Could you please elaborate on #2 comment. I didn't understand the purpose. I am 
using 3.2.0 version and facing the same problem. Adding initializeTranscoders 
property by default set to false prevents the error, though I am not sure of 
it's repercussions.

Original comment by [email protected] on 9 Jul 2013 at 1:43

[GoogleCodeExporter]

In 3.2.0 a new property was added to CacheFactory: initializeTranscoders. When 
it set to false (by default it is true) then SSM will not try to create 
automatically any Jackson objects. If you use only java serialization to store 
cached object (it's by default) then you don't need Jackson beans in SSM and 
can disable it. Disabling also allow you to use in your project other Jackson 
version than required by SSM. Previously even if JSON serialization in SSM 
wasn't used some Jackson objects were created at the startup and specific 
Jackson version on the classpath was required.

Original comment by [email protected] on 10 Jul 2013 at 4:50