Hello everyone! I wish to inform you that I am developing an application with Tiles 3 again. I don't know if I will help in development, but it is nice to see something familiar :-D
Now the real question. Currently the body in PutAttributeModel and AddAttributeModel is turned into a string and then set as a string value for the attribute. I think that this way of "serialization" is inefficient since the body is put in memory without real need. I think the best thing is to create a "body renderer" that acts like any other renderer. Since the Renderer.render wants a string as a first parameter, I think that a map: "generated name" -> body should be created in request scope. The name could be generated like in: CachingTilesContainer.getNextUniqueDefinitionName Do you think it is feasible. I mean, I guess that bodies of all supported technologies (JspFragment for JSP, ASTBlock for Velocity, TemplateDirectiveBody for Freemarker) can be moved around in the request and their evaluation is still correct, or not? Is there anything that I am missing? Moreover, the body can be evaluated at the "right" point, i.e. where the attribute is inserted, not where the attribute is put. WDYT? Moreover, since I am emeritus and I don't know if I will contribute much, what is the best thing to do for me? Should I fork a project in GitHub or resurrect my account for Tiles? Thanks in advance Antonio Petrelli
