Developer Studio on a non-English Windows OS (for example, Turkish) throws frequent java.lang.NullPointerException errors, gets permanently stuck on 'Code generation...', and produces numerous cannot-create/read/lock errors when generating code — changing the OS language isn't an option. What's causing this, and is there a workaround that doesn't require an OS language change?

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

This is generally caused by Developer Studio's own default file-encoding setting (UTF-8) not matching what the non-English OS locale actually expects for certain characters. The workaround is to override that default on the Developer Studio shortcut itself: locate the shortcut (for example, under the Start Menu Programs folder for your installed Developer Studio version), open its Properties, and append a locale-specific encoding switch to the Target field, like -J-Dfile.encoding=<locale-codepage> (for example, MS1254 for Turkish) — this needs admin rights to edit, since it's a shared shortcut. Once added, that locale-specific encoding switch overrides the default UTF-8 switch every time Developer Studio is launched from that shortcut, without needing to set it manually each session or change the underlying OS language.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions