I think at a point, where packaging by layer starts to become a serious handicap is where real modularity needs to come in. In most cases, even now in Java, it doesn't have to take much effort to make an application extensible via some sort of simple plug-in/module architecture. If you have that, then you can go with the flow and package by layer, and continuously factor out features into their own module containers. I think the current package structure in the Java language is insufficient for good, well, packaging of features, as it doesn't easily lend itself to metadata definition and each feature may easily contain classes that plug into different layers that need different levels of security. So I say, we keep using packages for layers and components/modules/plug-ins for features in conjunction with that.
On Jun 13, 7:15 am, Christian Beil <[email protected]> wrote: > Hi all, > > John O'Hanley (http://www.javapractices.com) has an interesting > article about harmful Java > practices:http://www.javaworld.com/javaworld/jw-07-2008/jw-07-harmful-idioms.html > > What is your opinion on that? I'm especially interested in what you > think about structuring packages? Do you package by layer (ie > dao,service,controller,...) or do you package by feature? > > Cheers, > Christian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
