On Sun, Sep 28, 2008 at 5:11 PM, Wendy Smoak <[EMAIL PROTECTED]> wrote: > > The archetype is encouraging the best practice of putting the Java > code in a separate module. > > If you need the directories, you can create them. If this is > something you need often, you can create your own archetype.
Ok interesting. Thanks Wendy. I didn't think of creating a separate module for the web-related java classes. Is this a common practice? I agree in separation of concerns, but that might be a bit much. In other words a servlet isn't going to be any good stand-alone (outside of the concept of web project) so it makes sense for me to have all that in a 'web module.' (Now if Eclipse supported multi-modules better I wouldn't' mind as much. I wish there was a way I could have a project in eclipse represented by the parent pom and then have all the sub modules beneath it. Back when I used IDEA, I think this was possible. Does NetBeans maybe support this?) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
