bad support of field with the following naming pattern aFIELD

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