On Apr 26, 2012 5:45 PM, "Francesco Chicchiriccò" <[email protected]> wrote: >
> > > No: one should first read the UserRequest object, then get UserTO / UserMod / userId (depending on the nature of the UserRequest: create / update / delete), next call the corresponding REST method on UserController, finally remove the UserRequest object. > > Are you proposing to encapsulate the logic reported above in a single REST method? It think it would make more sense to have a real workflow like for user objects underneath. That way the handling of the user request can be more configurable and would be more integrated in core. If I want a userrequest without the intervention of some conversion I have to implement this in the front end. It seems more logical to me to have that as a process in core. Of course at that point userrequest and user look very similar. Just my 2 cents of course. Cheers Bob
