Hi Christian,
In addition, there is an article on javapractices.com on the same issue: http://www.javapractices.com/topic/TopicAction.do?Id=205 My overall feeling is that package-by-layer is a wide habit, but one that is often worth breaking. In addition, a problem seems to be example code. People tend to naturally follow the style of code that is presented to them in examples. Unfortunately, even when a framework is compatible with package-by-feature, you will almost always see (in my experience) framework examples that use package-by-layer. One last comment: I find it interesting that modularity seems to be sensitive to what I call 'the simple deletion test': if the deletion of feature X is a single operation (for example, the deletion of a single file or a single directory), then the implementation is very likely modular. - John O'Hanley --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
