Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: Nightly Builds
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

      Description

      Currently strings are always considered as comma separated values and splitted
      into a List when added to a configuration. It is desirable to disable this
      feature sometimes though, that's why I'd like to suggest the addition of two
      methods getSplitStrings() and setSplitStrings(boolean) in the
      AbstractConfiguration class to affect this behaviour.

        Activity

        Hide
        Oliver Heger added a comment -

        (In reply to comment #3)
        > This issue has been fixed as part of the patch sent for COM-2240.
        > http://issues.apache.org/bugzilla/show_bug.cgi?id=35828
        >
        >
        Right! Closing this ticket now.

        Show
        Oliver Heger added a comment - (In reply to comment #3) > This issue has been fixed as part of the patch sent for COM-2240 . > http://issues.apache.org/bugzilla/show_bug.cgi?id=35828 > > Right! Closing this ticket now.
        Hide
        Jorge Ferrer added a comment -

        This issue has been fixed as part of the patch sent for COM-2240.
        http://issues.apache.org/bugzilla/show_bug.cgi?id=35828

        Show
        Jorge Ferrer added a comment - This issue has been fixed as part of the patch sent for COM-2240 . http://issues.apache.org/bugzilla/show_bug.cgi?id=35828
        Hide
        Oliver Heger added a comment -

        This idea is certainly worth a thought, but it may cause other problems:

        In the hierarchical configurations an extended syntax for querying properties is
        supported, which allows to address certain elements based on their index. So you
        can have something like

        config.getString("mylist.entry(1)");

        If we did not parse values when they are inserted, the implementation of this
        feature would be much more complicated. Situation becomes even worse when we
        want to support other query languages, e.g. XPath.

        Show
        Oliver Heger added a comment - This idea is certainly worth a thought, but it may cause other problems: In the hierarchical configurations an extended syntax for querying properties is supported, which allows to address certain elements based on their index. So you can have something like config.getString("mylist.entry(1)"); If we did not parse values when they are inserted, the implementation of this feature would be much more complicated. Situation becomes even worse when we want to support other query languages, e.g. XPath.
        Hide
        Jorge Ferrer added a comment -

        I'd like to propose a different solution: do not do the parsing until the
        getString or getList method is called. So if getString method is called
        delimiter is not looked for, but if the getList method is used then you should
        parse the string using the delimiter. IMHO this is a lot nicer and is what users
        would expect.

        Show
        Jorge Ferrer added a comment - I'd like to propose a different solution: do not do the parsing until the getString or getList method is called. So if getString method is called delimiter is not looked for, but if the getList method is used then you should parse the string using the delimiter. IMHO this is a lot nicer and is what users would expect.

          People

          • Assignee:
            Unassigned
            Reporter:
            Emmanuel Bourg
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development