[forge-issues] [JBoss JIRA] (FORGE-619) bad support of field with the following naming pattern aFIELD
George Gastaldi (JIRA)
jira-events at lists.jboss.org
Mon Aug 13 17:33:57 EDT 2012
[ https://issues.jboss.org/browse/FORGE-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
George Gastaldi updated FORGE-619:
----------------------------------
Fix Version/s: (was: 1.0.6.Final)
Git Pull Request: https://github.com/forge/core/pull/184 (was: https://github.com/forge/core/pull/184)
Forum Reference: https://community.jboss.org/message/751887#751887 (was: https://community.jboss.org/message/751887#751887)
> bad support of field with the following naming pattern aFIELD
> -------------------------------------------------------------
>
> Key: FORGE-619
> URL: https://issues.jboss.org/browse/FORGE-619
> Project: Forge
> Issue Type: Bug
> Reporter: Anthony Patricio
> Assignee: Richard Kennard
>
> Step to reproduce the issue, create an entity from forge with a field named aFIELD
> Check the get/set generated method,
> As per the javabean naming convention, we should have getaFIELD,setaFIELD but we have getAFIELD setAFIELD.
> When generated by eclipse then scaffolding, problem can appear, more important if the id is following the same naming pattern.
> Richard fixed almost everything related to meta widget.
> However the ForgePropertyStyle still needs some polishing.
> Check the forum reference.
> Cheers
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the forge-issues
mailing list