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

JcrConfigurationSource is lagging behind its Yaml counterpart

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Neutral
    • None
    • None
    • configuration
    • None

    Description

      JcrConfigurationSource currently does a few things wrong:
      Compare info.magnolia.config.source.jcr.JcrConfigurationSource#newProvider with info.magnolia.config.source.yaml.YamlConfigurationSource#loadAndRegister

      • errors are lost instead of being kept in the provider for further inspection
      • metadata is created using information from the bean, which prevents the above (metadata HAS to be there for the definition to be registered)
        • as a consequence we could be accidentally registered an "empty" provider

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              mgeljic Mikaël Geljić
              gjoseph Magnolia International
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Bug DoR
                  Task DoD