[forge-issues] [JBoss JIRA] (FORGE-619) bad support of field with the following naming pattern aFIELD

[Lincoln Baxter III (JIRA)]

    [ https://issues.jboss.org/browse/FORGE-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710546#comment-12710546 ] 

Lincoln Baxter III commented on FORGE-619:
------------------------------------------

I don't see a forum topic with that name. Do you have a link? Thanks, sorry.
                
> 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
>             Fix For: 1.0.6.Final
>
>
> 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