RequestBodyConverter for more than one argument

[farconada]

This converter only support one method argument, isnt it? see body paramater {"name": "Post 1", "body": "This is a blog post"}

instead if you use:
{"post": {"name": "Post 1", "body": "This is a blog post"}}
you could attach more than one parameter i.e
{
"post": {"name": "Post 1", "body": "This is a blog post"},
"anotherparam": {"text": "the text"}
}
also you could have a configuration parameter to enable if request parameter conversion is wrapped by a root tag

[tystr]

Indeed, I do see the use case for configuring the root parameter name to allow deserialization of request bodies like {"post": {"name" : "post 1"}}, but I'm not sure about allowing multiple roots like your second example, as this seems to go against REST principles of modifying a single resource.

[tystr]

It seems this may need to be handled by the serializer. For example, using jms serializer, this use case is handled for xml via the @XmlRoot annotation. http://jmsyst.com/libs/serializer/master/reference/annotations#xmlroot

[tystr]

I believe you could write a custom deserialization handler for jms serializer to handle the root tag bit. Another less ideal alternative/workaround could be to use a wrapper object for deserialization:

class UserWrapper
{
    /**
     * @var User
     * @Type("User")
     */
    protected $user;
    // ...
}