Uploaded image for project: 'Hippo CMS'
  1. Hippo CMS
  2. CMS-1071

Clean up extension points in plugin configuration

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • High
    • Resolution: Fixed
    • 2.01.00m06
    • 2.01.00m06.1
    • front-end-core
    • None

    Description

      Currently all plugins that contain child plugins should explicitly call addExtensionPoint(String name) for each child plugin.
      As a convenience Renderservice now checks for the existence of a (multi-value) property ''wicket.extensions' and if it exists it will call addExtensionpoint.

      This means that all explicit calls to addExtensionPoint can be removed (and added to the configuration of course)

      Also it is important to make it easy to distinguish between extension point configuration properties and 'normal' plugin-specific configuration properties.
      This can be done by using a simple naming convention: all extensionpoints start with 'extension.'

      Attachments

        Activity

          People

            wander grevink Wander Grevink (Inactive)
            wander grevink Wander Grevink (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 1 day
                1d
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 day
                1d