If I use the taglib for business logic (modifying the db), I have to put my code in JSP's. I really don't want to get into that habit. I also won't work for background processes (no JSP there)
The exceptions are a nice addition in 1.8, didn't know about that yet. POJO's are still my prefered programming model (at least for business logic). It leads to more readable code and you can use typed collections: List<NewsItem> items; is better than: List<Node> item; List<Node> could be considered a typed collection, but is just a List<Object> in MMBase lingo. Edwin -----Oorspronkelijk bericht----- Van: [EMAIL PROTECTED] Edwin van der Elst wrote: >When you actually develop application with MMBase, you tend to program > to the cloud-API, not use the taglib. That depends. I usually limit myself to taglib if possible, because that avoids a lot of complexity. [cut] > - No mapping to POJO's > This means that you have to call 'node.getStringValue() etc.' methods > all the time, can make errors in names of fields (going unnoticed for > a long time, given the 'nice' default values instead of exceptions) 1.8 throws exceptions here. (unless you switch that off again). Michiel -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.392 / Virus Database: 268.5.6/337 - Release Date: 11-5-2006 _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
