Hi, The current implementation of the LeafInclude (and LeafFile) tags from the MMBase taglib don't take into account the possibility of builder inheritance. We here at EO think that that it should, since it makes LeafInclude quite a bit more powerful.
Let's look at the following example: Object '1' is of type 'portal' Object '2' is of type 'map' Object '3' is of type 'blaat', where the 'blaat' builder extends from the 'map' builder. When doing a leafinclude for file 'doh.jsp' using the objectpath '1,2', the following paths are evaluated, and the first matching file is used: (note that I abbreviate the paths returned by getSmartPath() to the objectnumbers. See LeafInclude documentation for more information). /1/2/doh.jsp /1/map/doh.jsp /portal/map/doh.jsp The same would happen for objectpath '1,3', but we think it would be better to evaluate the following paths: /1/3/doh.jsp /1/blaat/doh.jsp /1/map/doh.jsp /portal/map/doh.jsp Note the extra path: '/1/map/doh.jsp', which is currently not evaluated by LeafInclude. Since object '3' is also a 'map' object, we think it would be logical for LeafInclude to also try this path for evaluation. Any thoughts on this? If I would implement this, is it a bugfix then? Something to check in into the 1.6 branch? Johannes Verelst Evangelische Omroep -- [EMAIL PROTECTED] | It is always possible to aglutenate multiple [EMAIL PROTECTED] | seperate problems into a single complex inter- [EMAIL PROTECTED] | dependent solution. In most cases this is a PGP ID: 0xFED127BD | bad idea. (RFC 1925, Truth 5)
