Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-4397522

Read only status of file.encoding varies by platform

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not an Issue
    • Icon: P3 P3
    • None
    • 1.3.0
    • core-libs



      Name: skT45625 Date: 12/12/2000


      Windows: java version "1.3.0"
      Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0-C)
      Java HotSpot(TM) Client VM (build 1.3.0-C, mixed mode)

      Linux:
      java version "1.3.0"
      Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0)
      Java HotSpot(TM) Client VM (build 1.3.0, mixed mode)



      file.encoding is read-only with linux jre 1.3, but Windows
      98 1.3 jre allows file.encoding to be set on command line
      (both java and javaw).

      Example a: In windows 98 'java -Dfile.encoding=bogus foo'
      yields "Error occurred during initialization of VM
      java/lang/ClassNotFoundException: sun/io/CharToBytebogus"

      Example b: Under linux 'java -Dfile.encoding=bogus foo'
      yields "Exception in thread "main"
      java.lang.NoClassDefFoundError: foo"
      (Review ID: 113683)
      ======================================================================

            ilittlesunw Ian Little (Inactive)
            skondamasunw Suresh Kondamareddy (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: