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.
Currently, netbeans allows you to execute an applet using the JDK's appletviewer, but it does not easily allow you to execute an applet with a web browser such as Netscape or Internet Explorer (using their own built in JVM, not the plug-in). This makes it very tedious to test Java applets that rely upon the browser's features/environment. To enable this to work, the CLASSPATH environment variable needs to be able to be set (as both Netscape and Internet Explorer use the CLASSPATH environment variable). The following is a comment from Jesse Glick "probably adding env vars to applet execution should be possible; please file an enhancement request against applet module. Currently it seems AppletExecutorBeanInfo specifically excludes most things from general external execution as most are inappropriate; this property could reasonably be left in, I think.". FYI.. I am opening a seperate related enhancement request (as suggested by Jesse Glick) that requests that environment variables allow tags to be substituted in them (e.g. {filesystems}) to simplify setting the CLASSPATH environment variable. Without this seperate enhancement, it would mean the user would have to manually type in the full classpath (which could be very long) into the environment variable settings.
FYI.. The related enhancement request is 12570.
I don't understand why it is so important to pass CLASSPATH to web browser. The classes related to applet are deliver by internal HTTP server from IDE
Yes, the internal HTTP server sounds like what I want. It is only mentioned a couple of times in the netbeans help and unfortunately is not mentioned in the areas relating to applets. The help needs to be improved by: 1. In the help topic "Configuring the Applet Executor", it should give an example of setting up a third party browser to execute the applet. In the example it should describe the {url} argument that can be specified in the "Arguments:" field in the "Property Editor: External viewer (NbProcessDescriptor)". For example, mentioning that the host name and port portion of the url are built from the internal HTTP server settings. I feel it is important that the {url} parameter is described, as it is not obvious that this is going to be a url to the internal http server, one could have assumed that it was a file url. 2. Providing a links in the help from the "Configuring the Applet Executor" topic to the "Configuring HTTP Server Options" topic.
Target milestone -> 3.3.1.
The help page that describes the applet executor now includes a description of the {url} parameter and includes a link to Configuring HTTP Server Options. The change was committed to the orion_fcs release branch.
Target milestone was changed from '3.4' to TBD.
Related to extbrowser. I am reassigning to Martin
Actually this might be easier to implement in 4.x using nbbrowse task. Of course UI for adjusting preference how to execute it needs to be defined.