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

beanification: reading configuration structures, allow class definition per node, support maps

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • 3.1 M1
    • None
    • core
    • None

      I started to improved the ContentUtil.setProperties() method and wrote a general configuration reader. I will put this into another util class or package. How ever Gregory is working on a similar system based on xsteram and jcr and as we know we use openwfe's encoder/decoder. What I have written is not meant to be a persistance mechanism but a tool to read configuration the way magnolia configuration is defined in general.

      It is very likely that this code will be replaced by Gregories work once we have internal jcr nodes and his work is finished. For now I would like to motivate everyone to use the toBean(node) methods where every they transform configuration to beans. This will improve the flexibility of magnolia a lot:

      • you can define implementing classes by the class property
      • additional properties (not forseen in the original class) are set as well
      • maps are supported in a simple way

      Example (orginal reason: filter bypasses and virtual uri mappings can be any kind of implementation and are much flexibler (and faster) therefore. This allows user based mappings or what ever you can think about.

        Acceptance criteria

              pbaerfuss Philipp Bärfuss
              pbaerfuss Philipp Bärfuss
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: