You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@freemarker.apache.org by "Daniel Dekany (JIRA)" <ji...@apache.org> on 2016/03/27 12:00:29 UTC

[jira] [Resolved] (FREEMARKER-18) JSP EL function and custom tag with the same name overwrite each other

     [ https://issues.apache.org/jira/browse/FREEMARKER-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Dekany resolved FREEMARKER-18.
-------------------------------------
       Resolution: Fixed
         Assignee: Daniel Dekany
    Fix Version/s: 2.3.25

Fixed in 2.3-gae branch. If an EL function and a JSP custom tag clashes, we produce a single FTL value that can be called both as an FTL function and as an FTL directive.

> JSP EL function and custom tag with the same name overwrite each other
> ----------------------------------------------------------------------
>
>                 Key: FREEMARKER-18
>                 URL: https://issues.apache.org/jira/browse/FREEMARKER-18
>             Project: Apache Freemarker
>          Issue Type: Bug
>          Components: jsp
>            Reporter: Daniel Dekany
>            Assignee: Daniel Dekany
>             Fix For: 2.3.25
>
>
> If a tab library contains both a function and a custom tag with the same name, they will overwrite each other. The one whose XML element in the TLD comes later wins (which for a valid TLD means that the function wins). That's first and foremost a backward compatibility problem, as before 2.3.22 the custom tag always won, because the function was ignored. Starting with 2.3.22 it can happen that you get a function instead of the custom tag, breaking an earlier working template. Also it would be good if we can support both behavior on the same time, be implementing both the {{TemplateMethodModelEx}} and the {{TemplateDirectiveModel}} interfaces.
> This problem was originally reported here: http://stackoverflow.com/questions/36086025/custom-tags-dont-work-in-freemarker-after-updating-to-version-2-3-22/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)