freemarker-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Dekany (JIRA)" <>
Subject [jira] [Commented] (FREEMARKER-55) FM3 freemarker-spring module, Web MVC support
Date Fri, 14 Jul 2017 08:41:02 GMT


Daniel Dekany commented on FREEMARKER-55:

At the first glance {{RequestContext }} doesn't expose the request/session/application attributes
and request parameters. However, there are options in {{AbstractTemplateView}} to add such
attributes to the model (not grouped by scope though). I haven't dig into this, but maybe
then these {{FreemarkerServlet}} variables shouldn't be there in Spring. Just a thought tho',
I have no experience with this.

BTW, the official name of the project is {{FreeMarker}} with capital {{M}}. The {{FreemarkerServlet}}
class from FM2 is not consistent with that, and it should be renamed in FM3. The new {{FreemarkerView}}
and {{AbstractFreemarkerView}} classes should also be renamed.

> FM3 freemarker-spring module, Web MVC support
> ---------------------------------------------
>                 Key: FREEMARKER-55
>                 URL:
>             Project: Apache Freemarker
>          Issue Type: Task
>    Affects Versions: 3.0.0
>            Reporter: Daniel Dekany
> Add Spring "Web MVC framework" functionality to freemarker-spring.
> This can be complex task (and the issue possibly has to be subdivided), as it involves
things like:
> * Some aspects of the FreeMarker 2 integration (developed by the Spring developers) are
quite confusing ({{FreemarerConfigurer}}, etc.), and we are looking into if it needs to be
like that.
> * See if we can support {{@EnableWebMvc}} (note that FreeMarker 2 support is hard coded
into {{ViewResolverRegistry}}, which we can't modify)
> * Creating custom directives/methods to expose Spring features like the Spring JSP Tag
Library does (but in a way that firs FreeMarker better)
> * Expose JSP custom tag support from the {{freemarker-servlet}} module.
> Depends on: FREEMARKER-54

This message was sent by Atlassian JIRA

View raw message