>-----Original Message----- >From: Scott Wilson [mailto:[email protected]] >Sent: Thursday, June 28, 2012 4:35 AM >To: [email protected] >Subject: Re: [Proposal] Model Isolation > >On 28 Jun 2012, at 03:41, Chris Geer wrote: > >> On Wed, Jun 27, 2012 at 6:50 PM, Franklin, Matthew B. >> <[email protected]>wrote: >> >>> Chris asked the question in the past if we wanted to move all models to >>> using IDs to reference related objects. I think this approach makes sense >>> in certain cases and tight coupling makes sense in others. I have put >>> together a proposal for a balanced approach in the wiki [1]. >>> >>> Given that each of these changes should be isolated enough, I think we >can >>> safely do this in trunk one class at a time. >>> >>> Thoughts? >>> >> >> I think we could even get away with combining Page and Widget groups. >Those >> are pretty tightly linked and probably won't be separated. >> >> One thing to consider though is how does a tightly coupled data model work >> for the various APIs? I've only done a little research but it looks like >> the REST API returns/accepts a pretty shallow data model. Would that cause >> problems with a richer backend data model? > >I think it may make sense to decouple the REST API data model from the >underlying model with some DTO classes representing just the data we want >to expose.
I agree, though I would say judicious use of DTO classes. I think we can handle things fairly easily in most cases. > >> >> Chris >> >>> >>> [1] : >>> >http://wiki.apache.org/rave/ArchitectureTopics/Persistence/ModelIsolation >>> >>> -Matt >>>
