> > like a user DAO or DTO that might be used in almost all > the features? > I think a core/common feature would be a great place to put it. To not expose dependencies of core to other features I'd also introduce a common feature that all features can depend on, then common can be implemented by stuff in core.
On Monday, August 10, 2009 2:57:46 PM UTC+2, Rob Wilson - BabyDuke JUG 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 "Java Posse" group. To unsubscribe from this group and stop receiving emails from it, send an email to javaposse+unsubscr...@googlegroups.com. To post to this group, send email to javaposse@googlegroups.com. Visit this group at http://groups.google.com/group/javaposse. For more options, visit https://groups.google.com/d/optout.
