[
https://issues.apache.org/jira/browse/MYFACES-3810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe resolved MYFACES-3810.
-------------------------------------
Resolution: Fixed
> Add compatibility mode for facelets 1.1.x behavior
> --------------------------------------------------
>
> Key: MYFACES-3810
> URL: https://issues.apache.org/jira/browse/MYFACES-3810
> Project: MyFaces Core
> Issue Type: Task
> Components: JSR-344
> Reporter: Leonardo Uribe
> Assignee: Leonardo Uribe
> Fix For: 2.2.0
>
>
> Some big improvements and fixes has been done over the time in MyFaces 2.0.x
> / 2.1.x . But on the way some changes were done over some tags like:
> - c:set
> - ui:param
> - user custom tag handlers
> And others. See this issues:
> - MYFACES-3169
> - MYFACES-2753
> - MYFACES-2293
> The current changes are completely justified and there is no turning back.
> These changes are very important to allow techniques like EL expression
> caching to work correctly.
> But it is also true that Mojarra still has the old behavior, and there are
> still web applications out there that relies on that behavior. Users trying
> to migrate from Mojarra to MyFaces usually found this problem.
> The proposal for this issue is create a web config param called
> org.apache.myfaces.STRICT_JSF_2_FACELETS_COMPATIBILITY by default false that
> when is enabled, the old way to do things is activated. Legacy versions of
> c:set, uiparam and user tag handler are activated. The aim is just provide a
> workaround for those cases and incentive users to change their application
> code to a more standard and stable form.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
