Uploaded image for project: '[Read Only] - Hippo Site Toolkit 2'
  1. [Read Only] - Hippo Site Toolkit 2
  2. HSTTWO-4577

Use HippoEssentialsGenerated annotation instead of AutoEnhancedBean

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 13.2.0
    • Component/s: None
    • Labels:
      None
    • Processed by team:
      Pulsar
    • Sprint:
      Platform 205 - Content Beans 2, Platform 206 - Content Beans 3

      Description

      We implemented AutoEnhancedBean annotation to support enhancing of the existing beans. But the essentials has also HippoEssentialsGenerated annotation. For the existing beans, the same annotation could be used instead of using the AutoEnhancedBean annotation to decide which beans will be generated on the fly. Having two different annotations could be confusing for the developers and if the developer wants to make the beans up-to-date in all time then he needs to add the AutoEnhancedBean annotation to all existing beans.

      If HippoEssentialsGenerated is not defined or it is defined with allowModification field as true then the new beans will be generated. If the allowModification is set as false, then the bean won’t be generated. Besides this, if the existing bean is up-to-date, then the new class wouldn’t be generated and the existing bean will be used.

      In addition, we could add a system property to be able to disable/enable dynamic bean feature.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            cgul Cuneyt Gul
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: