This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
When executing JavaFX project from NetBeans as an applet, JVM Arguments (Properties->Run) are not passed to the applet, even though they can be set by the user (the "JVM Arguments" text box is not disabled). In cases when specific runtime conditions, such as larger than default Java heap size, are required, there is no easy mechanism to pass the JVM Arguments.
Passing JVM arguments to a WebStarted applet is quite different and limited just to initial-heap-size and max-heap-size. Enabled UI control in Project Properties that does not have any function in the selected context can be considered as P4 priority. I would rather mark it as RFE to support at least initial-heap-size and max-heap-size for the applets.
Before parking this issue as P4, please provide a workaround as it's a production use case.
Currently you can manually modify generated JNLP descriptor and add initial-heap-size and max-heap-size attributes to the <j2se> element. I am keeping this as P1 RFE as it requires extension of the javafxpackager commandline options and several other modifications in NetBeans. Until now it never happend that some developer would create so big Applet that it runs out of memory and without knowledge of WebStart technology and JNLP descriptor. You are the first reported case so we have to implement a new feature for you. BTW where these production cases come from if you don't know even the theoretical solution? NetBeans is just high-level IDE, we cannot change the technologies used for JavaFX. For these production cases we can just create some UI element for particular command line option of the JavaFX SDK tools.
Closing all bugs filed against JavaFX 1.x as wontfix. We will support JavaFX 2.0 - please keep opened only bugs against the new release. Thanks.