Design - How Map Request Parameters Data To Domain Model

This is a design question is the same problem in any language.as you do to map the controller to the domain model?We have situations in general larger than ... consider the example objects .

situation.1 - We have a request that has all the parameters of the account ;{ " id" : " 1 " , "name " : "test " , "some " : " xxx " } ............. and other fields .

situation.2 - can request that has to have a certain account parameters , for example in the case of an update;{" id" , " 1" , "name " , " testUpdated "}

situation.3 - We have a request that has some parameters of the account , others have more like id as user together;{ " id" : " 1 " , "user " : " xxx " , "service " : " yyy " } in which case each piece of the request will turn an object .

Java Code:

public class Account {

private Long id;
private String name ;
private String some ;

} mh_sh_highlight_all('java');

I see a few options ;

1 - Can I get AccountForm in the controller and set the properties for the Account object and others in CONTROLLER ;

+ ok for situation.1 situations 2, and situation.3

+ Separates the requisition of the object domain

- Pollutes the controller with code conversion

- Controller is full of setters .. if a higher class as a large object as a request is very confusing .

Java Code:

controller ( AccountForm from ) {
Account account = new Account ( )
account.setNome form.getNome = ();
account.setSome form.getSome = ();
Other outher = new Other ( ) ;
other.setSome ( form.getSome ( ) ) ;
} mh_sh_highlight_all('java');

2 - Can I get AccountRequest in the controller and have a method in itself as AccountRequest.getAccount ( ) to return a mapped model , in this case the mapping is at own Request object .

+ Separates the requisition of the object domain

+ Encapsulates the conversion in a place with easy access .

+ Meets situation.1 situation.2 and situation3 ;

- Request object has two responsibilities represent the request and map to a valid model .

Java Code:

controller ( AccountForm accountRequest ) {
Account account = accountRequest.getAccount ( ) ;
Outher outher accountRequest.getOther = ( )
} mh_sh_highlight_all('java');

3 - Can I get the controller Direct Account which had been filled with nulls .

+ Eliminate object request

- Serves only situation.1 situation.2 .

Java Code:

controller (Account account ) {
account.someMethod ();
} mh_sh_highlight_all('java');

4 - Outsource this mapping request parameters to another object mapper for request ..

+ Isolates logic mapping

- Until complexity for simpler cases are used as standard for all such a find by id .

- One more class for each request ;

In the case of API gets worse response has two further classes. speaking in terms of request for response .... AccountRequest, AccountRequestMapper, Account, AccountResponseMapper, AccountResponse .....I'm doing more testing the Hybrid option 3 for simple cases (find ID or updates) .... with option 2 for example for more complex cases ..