---

Java Documentation (developer)

Radar #4451855

BigDecimal Backward Compatibility

Description:

In J2SE 5.0, BigDecimal.toString() returns a value using scientific notation instead of the value as a string, the standard behavior in Java 1.4.2.

Workaround:

Calling BigDecimal.toPlainString() returns the value as a string.

Radar #5226690

Bundled applications cannot run in 64-bit mode

Description:

Bundled Java applications deployed on 64-bit Intel machines cannot be forced to use a particular architecture by clicking a checkbox in the Get Info panel for the application.

Resolution:

If you want your bundled Java application to run in 64-bit you need to make the following changes to the Java dictionary in the Info.plist file. -- Set the value of "JVMVersion" to 1.5* or 1.5+. -- Add an array element named "JVMArchs". Each of the elements must be of type String, and specify the order of preference for architectures. The available architectures of the machine running the application are compared against this list, and the first one that matches is chosen. For example, <key>JVMArchs</key> <array> <string>x86_64</string> <string>i386</string> <string>ppc</string> </array> would choose 64-bit Intel if available, then i386. If the application is run on Power PC hardware, it will run as it did before Mac OS X 10.5. If you specify a list and none of your choices could not be satisfied, the application will not launch.

Radar #5422774

Running Java applications in 64-bit mode

Description:

Java 1.5 on Mac OS X 10.5 will run in 64-bit mode, but the command line 'java' will use the 32-bit Java VM by default.

Resolution:

To specify the architecture you want, use '-d32' or '-d64' to indicate which Intel architecture you want to use. If the specified architecture is not supported the default architecture will still be used.

---