Uploaded image for project: 'Log4j 2'
  1. Log4j 2
  2. LOG4J2-2674

CompositeConfiguration misleading configuration source

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Trivial
    • Resolution: Fixed
    • Affects Version/s: 2.8.1
    • Fix Version/s: 2.13.0
    • Component/s: Core

      Description

      Sometimes we are using CompositeConfiguration in our code. During last investigation we've found out that configuration source passed during constructor call is 'NULL_SOURCE'. It's a bit confusing because it conflicts with NULL_SOURCE definition

          /**
           * ConfigurationSource to use with Configurations that do not require a "real" configuration source.
           */
          public static final ConfigurationSource NULL_SOURCE = new ConfigurationSource(new byte[0]);
      

      because actually we have a 'composite' or 'multiple' configuration sources which will be used later to produce real configuration.

      The question is: do you mind to create 'COMPOSITE_SOURCE' constant and use it in CompositeConfiguration?

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                korenkov Anton Korenkov
              • Votes:
                1 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 10m
                  10m