JNI Invocation API strings not UTF-8

XMLWordPrintable

    • Type: Enhancement
    • Resolution: Won't Fix
    • Priority: P3
    • None
    • Affects Version/s: 1.4.1_02
    • Component/s: hotspot
    • unknown
    • other

      In struct JavaVMOption, char *optionString is obviously not expected by the Invocation API to be encoded with Java's modified UTF-8, but rather with a "platform" encoding somehow derived from the OS environment. This makes it impossible for a client of the Invocation API to reliably pass in any Unicode optionStrings. Also, the documentation of the Invocation API lacks a description of how those strings should be encoded.

            Assignee:
            Unassigned
            Reporter:
            J. Duke
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: