Michiel Meeuwissen wrote:
Ernst Bunders wrote:
- 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)
This is particularly unfortunate becouse mmbase nodes can not be used in
combination with jstl and expression language, as methods such as
node.getStringValue("name") are not supported bij expression language.
This stands in the way of using mmbase for building mvc webapps.
This is not true. In 1.8 the following works:
<mm:node id="mynode" >
${mynode.title}
</mm:node>
and even anonymously:
<mm:node>
${_node.title}
</mm:node>
This works by using org.mmbase.bridge.util.NodeMap (a map which still is
a node), and can work because EL also supports maps. So, if your MVC
fills the request-attributes with node objects it can do the same and
wrap them in such a NodeMap, and they can perfectly naturally be used in
the view.
well, dammit boy, do you ever sleep?? :-)
ernst
Michiel
_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers
