Hi Davis, In that case, you have to go with a /thin/ domain model where your business objects are not more than value objects. This is actually a foremost design decision and in that case, you are right. But I /personally/ don't like these types of models since you are forced to break OO encapsulation sooner or later...
Regards, Vincent PS: I also like design discussions Davis Ford a écrit : > Hi Vincent -- I like design discussions :) > > In this case, I really don't think it warrants an extra layer. That, > to me, seems like more maintenance. If my entity objects are fairly > simple -- and they are, why do I need an extra layer of transformation > when Gas3 gets me *almost* all the way there. > > In any event, I've been exchanging with Franck on the graniteds list, > and he's just released a fix for the URL issue, and he is going to add > annotation support to allow control for generation. > > Currently, if you specify a field as transient: > > private transient Object someObject; > > Gas3 will ignore it in the generation. However, this is no good, b/c > it conflicts with JPA. If it is marked as transient in JPA it will > also ignore it for the database, which is not what I want. If he adds > a custom annotation, I can control it via that, and all is well. > > Regards, > Davis > -- Vincent Vandenschrick Jspresso Framework http://www.jspresso.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Flex Mojos" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/flex-mojos?hl=en?hl=en http://blog.flex-mojos.info/ -~----------~----~----~----~------~----~------~--~---
