Properties.load fails to throw IAE on malformed unicode in certain circumstances

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: P4
    • 13
    • Affects Version/s: 5.0, 6, 7, 8, 11, 12, 13
    • Component/s: core-libs
    • b24

        A property file like the following should fail to load with an IAE

        a=\u0

        but if there's a preceding property like this, it might mis-parse instead:

        b=\u0123
        a=\u0

        -> property a erroneously becomes \u0123

        Fixing this might mean some properties files that were malformed would go from being silently misparsed to throwing an IllegalArgumentException, so a CSR will be filed.

          There are no Sub-Tasks for this issue.

              Assignee:
              Claes Redestad
              Reporter:
              Claes Redestad
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: