Closed sdeleuze closed 11 years ago
This fix has been validated with a sample app based on multi-module archetype + using contract module with spring-amq-hessian RPC client/server
Way better. But one thing is still not clear: why are we persisting a DTO through a service?
I thought the main purpose of this archetype was decoupling DTOs+external services interfaces from model+internal services. If the model/dto changes, the whole stack has to be updated, which is not what we aimed for.
Will try another way, this one is not clean enought
... with improved implementation of contract module and SampleService/Sample/SampleController classes. Need to update documentation to provide guidance for DTO usage (not used here since we use model based POJO with generic ServiceBasedController)
Previously, DTO and Service were here but not used, that was very confusing as described in RESThub discussion group https://groups.google.com/forum/?fromgroups=#!topic/resthub-dev/vYpt3kB_d-4
Depend on https://github.com/resthub/resthub-spring-stack/pull/153