This sort of thing is terribly difficult to discuss without concrete examples. For shared domain stuff, you can usually still identify an intersecting level higher up in the hierarchy no and aim to have these as abstract as possible no? In some ways it reminds me of the hard part of doing REST, you can't just throw your stuff into a bucket, you really need to think hard about it and give refactoring tools their prime time.
/Casper On 10 Aug., 14:57, 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 -~----------~----~----~----~------~----~------~--~---
