I agree with Rick, if you have servlets, filters, even actions (struts, webwork, etc.) i think there is no need to separate the code from your web module (if your views depends on it). Nevertheless, separating the code from the views it's a very elegant approach...
If the Eclipse workspace wasn't flat, I think it would be easier and pretty much straightforward to work with multimodule projects. It can be really messy if you have, let's say, three or four projects with 4 or five different modules. But that's just my opinion. I read somewhere that the Eclipse guys were considering to change it's workpace structure in future releases... But like Graham said Eclipse does support multimodule projects (of course with the help of the maven eclipse plugin!!!) Regards people... On Sun, Sep 28, 2008 at 4:27 PM, Graham Leggett <[EMAIL PROTECTED]> wrote: > Rick wrote: > > (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?) >> > > Eclipse does support multi-modules, use it all the time. > > Make sure that your eclipse config is generated by the maven-eclipse-plugin > to do this the easy way. Each module of a multi-module project will be added > as a project dependency (instead of a jar dependency) in eclipse. > > Regards, > Graham > -- >
