On 8/21/07, benoit moraillon <[EMAIL PROTECTED]> wrote: > Hi appfusers, > appfuse:full-source is a very good idea, more productive and more > comfortable for webapp developpement. > > > But... > I think having both applicationContext.xml in webapp/web-inf and > application-dao.xml, -service.xml in src/main/ressources is confusing. I > think appfuse should reduce the number of configuration files and sources > directory in order to be easier to learn and use.
What would you prefer? One file with a whole bunch of bean definitions? The files and their locations make much more sense when you look at AppFuse in SVN. Each module contains its own Spring context file. When you aggregate them together, it is a bit different, but if you know what goes where, I don't think it's too bad. In AppFuse 1.x, we told users to put DAOs in applicationContext-hibernate.xml, Managers in applicationContext-service.xml and everything else in other files. Not much has changed over the years. > > Better directory organization + Less configuration files = better > productivity and better developpment comfort The directory organization is based on Maven's standard directory layout. http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html IMO, directory layout shouldn't matter - just use Ctrl + Shift + R in Eclipse (and Ctrl + Shift + N in IDEA) to find files and it shouldn't matter where they're located. Use your IDE = better productivity. ;-) Matt > > Best regards, > > -- Benoît Moraillon > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- http://raibledesigns.com
