A few months ago I asked for ideas on project management, and you all gave
me some great suggestions of tools and books to check out. Now I'd like to
hear if anyone has recommendations for a resource that explains how to tie
the web application together -- what I would call architecture.
I'm
I like Martin Fowler's Patterns of Enterprise Architecture. I also
like Eric Evans' Domain Driven Design.
As for your specific questions:
dao -- Outside of a reasonably simple crud application I wouldn't have
Wicket even aware of daos. I like to have wicket (or other clients)
talk to the
Good suggestions there. I also like the Enterprise Integration Patterns
book, but that might not be what you're looking for.
--
Nick Heudecker
Professional Wicket Training Consulting
http://www.systemmobile.com
Thanks for the well-expressed responses. I'll look into the books. Most of
my knowledge about web application programming theory comes from reading
lists like this. There are certain terms that pop up over and over again, so
eventually I think, That must be important, I guess it's time for me to
What we do is take all of our /DAO/Model 'stuff' and package it up into its
own jar file that is then included in any projects that require it. This
allows us to
A) Version our data systems without impacting the apps using them (mostly)
B) Gives us a unified data layer for all of our applications
