ICEfaces
  1. ICEfaces
  2. ICE-5922

ACE Generator use naming conventions

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.0-Beta2
    • Fix Version/s: None
    • Component/s: ACE-Components
    • Labels:
      None
    • Environment:
      sparkle

      Description

      Looking at a typical sparkle Meta class:

      @Component(
          tagName = "inputFiles",
          componentClass = "org.icefaces.component.inputFiles.InputFiles",
          rendererClass = "org.icefaces.component.inputFiles.InputFilesRenderer",
          generatedClass = "org.icefaces.component.inputFiles.InputFilesBase",
          extendsClass = "javax.faces.component.UIComponentBase",
          componentType = "org.icefaces.faces.InputFiles",
          rendererType = "org.icefaces.faces.InputFilesRenderer",
          componentFamily = "org.icefaces.faces.InputFiles"
      )

      We see that there are a lot of redundantly specified class names, which could be derived from the Meta class' own class name and package name. Or from the tagName.

        Activity

          People

          • Assignee:
            Unassigned
            Reporter:
            Mark Collette
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: