A short reaction to this MMBase taglib vs. JSP2 debate - I've been down that road already:
Regarding upgrading the MMBase taglib to support JSP2, just forget about it - it cannot be done. The taglib can be used in a JSP2 environment, but only in the backward-compatibility mode with support of expressions turned off. There is no way to overcome this without changing the functionality, since the context-variable notation used by the taglib collides with the expression language. In addition, whatever the outcome of such an upgrading attempts, it is bound to be hampered by legacy restrictions and a bad fit to a JSP2 environment. Alternatively, consider starting from scratch and implementing a new lightweight MMBase taglib geared towards JSP2. This is not as hard as it sounds, for a number of reasons: - creation of tags is easier in JSP2. - the JSP expression language can be used to exchange variables - JSTL functionality can be leveraged, so less tags are needed (iteration, conditions, formatting, conversions) As far as I'm concerned, such a taglib only needs to support presentation logic. In a Model2 architecture (now the industry standard for J2EE websites), business logic like creating/modifying/deleting nodes, does not belong inside JSP's. Nevertheless, when the need is felt, such business-logic oriented functionality can be provided in the form of an additional taglib, taking advantage of the fact that JSP2 allows taglibs to collaborate using expression variables. I'm presently working on a prototype for such a taglib as proof of concept and to play around with. I plan to make it available later on, following the release of MMBase1.7 - yes it can (and should) be distributed separately. Rob van Maris Technical Consultant Quantiq xmedia & communication solutions Koninginneweg 11-13 1217 KP Hilversum T +31 (0)356257211 M +31 (0)651444006 E [EMAIL PROTECTED]
