It was a while ago but V2 proposed to define the data used in view in xml. This would free us from the posrel problem in jsp pages. I think (like rico said) that the "A" current way to do this might be to have separates jsp (or jsp parts) to define the model used and to show the data. The can be used for the global structure of pages. On the other hand i dislike MVC because it's anty OO and you have to do everything 3 or more times.
And, in my view, MVC presumes that you can completely define your site's model beforehand. Which is maybe the case in some high profile web sites, but in most cases is not. It's not very iterative.
One of the concepts, i believe, that laid the fundament for the web was the iterative nature of HTML. You could (can) at every moment change the look of your page by fiddling with your HTML-tags. And that's also the nature of the current MMBase taglib, you can fiddle as much as you like until it looks right ;-)
I think MMBase could use both kind of logics, buth a taglib that is more suitable for 'iteratively' building smaller sites will be my favorite.
---Andr� -- Andr� van Toly http://www.toly.nl mobile +31(0)627233562 ------------------------------------------------------------------>><<-- _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
