Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-3521

PropertyInitializer should be pluggable.

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Neutral Neutral
    • None
    • 4.3.8, 4.4.1
    • core
    • None

      I don't know if it's un der refactoring right now, but just in case, I'm adding this.
      Most of the patch I submitted on this topic would have been simply avoided if the PropertyInizializer class could be specified somehow. It would be nice to have the PropertyInitializer class set (optionally) in the web.xml just like the magnolia.initialization.file. Something like magnolia.property.initialization.class = my.package.MyOwnPropertyInitializer. So Magnolia will delegate to the given class the property init, maybe with a fallback to the default one (more or less the current one). This shuold cover also most of the corner cases in configuration without overriding the PropertyInitializer each time.
      Maybe it could even be restored the simpler PropertyInitializer as the default one, leaving the contextpath/attribute/system extension to another class.

        Acceptance criteria

              Unassigned Unassigned
              dfghi Danilo Ghirardelli
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Task DoD