> > I'm working on upgrading Tiles plugin to use the latest Tiles 2.x > > version - 2.2.2 - and it looks like the only thing is to drop all the > > custom code from the plugin, just leave TilesResult. > > > > Tiles 2.2.2 contains support for FreeMarker (the Struts custom is > > doing that) plus few other features. I think the only thing would be > > writing a custom variable resolver to use Struts' ValueStack. > > > > Am I right? > > After playing a bit with different options I think I will leave > existing StrutsTilesListener (for easier migration) but will add > dedicated factory to support wildcards, EL, OGNL and Freemarker - it > looks far reasonable than using Tiles' CompleteAutoloadTilesListener. > Also I will make it more extensible for future extensions. > >
I'm not so deep into tiles to have a strong opinion. But that makes a lot of sense to me. Can this be shared between tiles2 and tiles3 plugins? Regards, Christoph This Email was scanned by Sophos Anti Virus
