Maybe "User" is just overloaded with meaning and should really be split up into multiple classes (or traits if you have them) each focused on their role in their respective package?
Or maybe "User" shouldn't be in any of them, maybe "User" is just the mechanics to implement a specific feature which should be isolated to its own "feature"-package implementing the services the other features need? BR, John On Mon, Aug 10, 2009 at 2:57 PM, Rob Wilson - BabyDuke JUG<[email protected]> wrote: > > I like the idea of organizing the packages by feature, but I wonder > where you put the common code, or code that is used in a couple of > places? For example, the domain objects might not fit exclsuvely in > one feature - like a user DAO or DTO that might be used in almost all > the features? > > I guess I would struggle to decide where supporting classes should > live, are there any tips to getting this right? > > Cheers, > Rob. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" 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/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
