Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-40249

Kernel > allow more flexibility in defining sakai.properties loaded with getPatternList() or getStringList()

    XMLWordPrintable

    Details

    • Type: Feature Request
    • Status: RESOLVED
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 12.2, 19.0
    • Fix Version/s: 19.0
    • Component/s: Kernel
    • Labels:
    • Test Plan:
      Hide

      Please add a Test Plan here.

      Show
      Please add a Test Plan here.

      Description

      Currently if you want to load some sakai.properties with either getStringList() or getPatternList(), the sakai.property must be defined as a single property with comma separated values:

      propertyName=value1,value2,value3
      

      If your list of values is really long (long text values, long or numerous regex patterns, etc.), the resulting property can be difficult to read and manage. Although the .count style of defining sakai.properties is "old", it can be really beneficial for situations like these to clean things up:

      propertyName.count=3
      propertyName.1=reallyLongValueWithOrWithoutRegex
      propertyName.2=reallyLongValueWithOrWithoutRegex
      propertyName.3=reallyLongValueWithOrWithoutRegex
      

      It's a relatively minor change to getStringList() (which is also used by getPatternList()) to support both styles of defining sakai.properties by simply using the existing getStrings() method rather than getString().

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                bjones86 Brian Jones
                Reporter:
                bjones86 Brian Jones
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Git Source Code