That's pretty accurate! You know, these reoccurring cycles could be patterned into framework base classes now that Java support generics. Db4o works fine in this manner and needs no 2D mappings at all. In fact, I have a single class that handles all persistence/search behaviors for all my actions. This persistence tier is largely transparent on my sites and I never really think about it. My life is centered around modeling the domain with POJOs (pronounced fun and easy) and of course arm wrestling the darn pages and tags!
P.S. Pages and tags suck Scott On Fri, Jun 20, 2008 at 7:24 AM, Antonio Petrelli < [EMAIL PROTECTED]> wrote: > 2008/6/20 Ted Husted <[EMAIL PROTECTED]>: > > But why does web application still seem so difficult or so > > time-consuming? > > IMHO it's the presence of too many layers of applications. For a > simple thing like a search result you have to do (for example in > Struts 1): > - the JSP page > - the DAO > - the service that calls the DAO > - the domain objects > - the action that calls the service, and the ActionForm > - the configuration of the action > - then go again to JSP pages to link actions together > > There are pieces that can be avoided, but the structure almost remains this > one. > I think that approaches like NakedObjects [1] and Roma Framework [2] > could help avoiding this tedious work. > Anyway there is always some work for adaptation on your particular > case, many times they seem to be a unique case that cannot be put in > the general vision of the framework, so you stick on coding it with > simple frameworks (like Struts 1) or no frameworks at all. > > Just my 2 eurocents > Antonio > > [1] http://www.nakedobjects.org/ > [2] http://romaframework.xwiki.com/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Scott [EMAIL PROTECTED]
