Hi Roy, >I vote yea for A, B, and C. I have already found myself implementing >these methods by hand and have been too lazy to say or do >anything about >it. ;-) I'm glad I'm not the only one having ideas like this :-)
>I am not sure I understand D, if you already have a factory method on >the DAO, why create a factory object as well? Yep, it would be somehow like this: - all file are generated the way they are today - additionally, we generate one Factory class for each and every entity, e.g. PersonFactory, BookingFactory, etc - this factory will only contain one method (i.e.: createPerson, createBooking, and so forth) I admit that this is a strange kind of design, but it is one of many possible solutions to the problem. Personally, I like option A (factory method on the Entity interface class) and B (factory method on the DAO) very much. I bet that Chad will suggest making this a configurable aspect of the spring cartridge, allwoing the user to decide whichever option he likes best. And if Chad would suggets something like this, I'd agree (hint, hint) :-) Peter ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
