I like this functionality, however I wish that the implementation was consistent with Spring's use of Jackson for @[email protected]
I already use Jackson annotations to define the desired codec for my web interface. It's a drag that when I turn around and
Json() the object returned from @RequestBody the json isn't the same that from Jackson. Not sure why @[email protected] uses Jackson and this plugin uses flexjson.
Jackson appears to have richer annotation support and is already the @REST default provider. I suggest keeping this plugin's API and migrating the provider from flexjson to Jackson.