[jira] Commented: (TRINIDAD-712) Do not generate final properties with the maven-faces-plugin

["Andrew Robinson (JIRA)" <de...@myfaces.apache.org>]

    [ https://issues.apache.org/jira/browse/TRINIDAD-712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12527895 ] 

Andrew Robinson commented on TRINIDAD-712:
------------------------------------------

This is not a correct assessment for a large portion of the time. Most of the time that the properties are used, they are used by people using binding. There are a lot of reasons to want to change this value before it is stored into the FacesBean. If JSF components weren't meant to have properties, then the faces plugin shouldn't generate them, and the attributes map should only be used. If you are going to create properties, you should give people the freedom to extend the components and customize the behavior.

> Do not generate final properties with the maven-faces-plugin
> ------------------------------------------------------------
>
>                 Key: TRINIDAD-712
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-712
>             Project: MyFaces Trinidad
>          Issue Type: Wish
>          Components: Plugins
>    Affects Versions: 1.0.2-plugins
>         Environment: maven-faces-plugin version 1.0.2 from the maven repository
>            Reporter: Andrew Robinson
>            Assignee: Adam Winer
>
> It would be extremely beneficial to not have property methods generated as final by the maven-faces-plugin. 
> IMO, final should be reserved for constants and only on methods with rare exceptions and good reasons.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.