> The advantage of not using Struts, is I think the original advantage of JSP > itself (vs. other Servlets). A simple JSP, with only non-specific taglibs > (like the mmbase taglib) can be quickly understood, and quickly > developed/bug-fixed, because there is no need to redeploy the complete > application on every iteration, and the functionality is not so easily > scattered.
Yes , and this is one of the attractive points of MMBase, (an other one is that you can add new object types and relation as time goes). This all helps in creating site fast. I prefer to look at mmbase as a Object database with a lot of functionality, so much that it is often not needed to use anything else. Still MMBase is not a framework and I think this very important. Techniques come and go (wml flash servlets jsp) but you know one thing for shure, if your information is stored in a semantic way in mmbase you can smile at the future. Using a framework will help in centralizing code , and will give you a standardized way to work it might introduce concepts that are not available in mmbase (form validation, multi-platform publishing , page flow , static site publishing, site branding, personalisation, work flow etc..). The drawback is that you then have to know how know more techniques. If I look at my experience the last few year i can say that the jsp/tablig works well for displaying data from mmbase and that when real user interaction is required (backend editors or dynamic sites) you need to write extra code. And that code has to live somewhere. -use builder functions -use an extra layer for storing logic. anyway I haven't build 1 mmbase site the last 3 years that did not contain java scriptlets in the jsp's or used a framework. I have always found cocoon an interesing frontend for mmbase (but that solves a different problem) what was the question?
