Uploaded image for project: 'Forge'
  1. Forge
  2. FORGE-619

bad support of field with the following naming pattern aFIELD

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      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

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                kennardconsulting Richard Kennard
                Reporter:
                AnthonyHib Anthony Patricio
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: