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

Leonardo Uribe resolved MYFACES-3715.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2.0

> Remove unnecessary parameters or features from earlier versions in MyFaces 2.2
> ------------------------------------------------------------------------------
>
>                 Key: MYFACES-3715
>                 URL: https://issues.apache.org/jira/browse/MYFACES-3715
>             Project: MyFaces Core
>          Issue Type: Task
>          Components: JSR-344
>            Reporter: Leonardo Uribe
>            Assignee: Leonardo Uribe
>            Priority: Blocker
>             Fix For: 2.2.0
>
>
> Before any release, it is necessary to remove unnecessary parameters or 
> features from earlier versions
> One example is org.apache.myfaces.HANDLE_STATE_CACHING_MECHANICS web config 
> param. It was added in 2.0.x/2.1.x to deal with StateManager implementations 
> that relies on previous behavior, but in 2.2.x, we should unify that part (ri 
> behavior).
> Other example is org.apache.myfaces.RENDER_FORM_SUBMIT_SCRIPT_INLINE web 
> config param. With the standard javascript api (jsf.js), this behavior was 
> included in the javascript file by default. The param was included only for 
> backward compatibility with previous versions (JSF 1.2).
> There are other examples of config params like org.apache.myfaces.PRETTY_HTML 
> that are only things left from 1.1.x versions. 
> It is necessary to do this part before any official release.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Reply via email to