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.
Forte for Java CE, build 010803 I created JApplet. When I start execution, then nothing happened. When I start debugging then I sew Debugging started, Debugging running and Debugging finished in very short time and nothing happened. I am able start appletviewer for may applet from console, but from IDE it doesn't work.
I have exactly the same problem with applet execution and debugging on Linux. FFJ, build 010803 JDK 1.3.1-b24 Mandrake Linux 8.0, kernel 2.4.3
Debugging / Execution of Applets works fine under NetBeans 3.2.1RC2 Build 89 JDK 1.3.1-b24 Windows 2000 SP1
This is caused by the fact that the Appletviewer launched by the execution somehow uses proxy to access the internal HTTP server (which serves the applet class and its containing HTML page). From the IDE log: [IDE-Exec] Executing: 0 .= C:\jdk1.3.1\jre\..\bin\appletviewer 1 .= http://ppisl-sun:8082/classpath/JApplet.html Note that even when using the command line, this does not work: C:\jdk1.3.1\jre\..\bin\appletviewer http://ppisl- sun:8082/classpath/JApplet.html This is because for some reason appletviewer accesses ppisl-sun machine through proxy. When changed so it uses 'localhost': [IDE-Exec] Executing: 0 .= C:\jdk1.3.1\jre\..\bin\appletviewer 1 .= http://localhost:8082/classpath/JApplet.html everything works.
This looks like a network configuration problem, because also other software running on the user's machine is affected, not just the IDE.
I have discovered the fault present in this bug... It isn't really a bug, it is more like a request for enhancement. When you build your JavaDoc from you own api, the java doc utility will create a directory sturcture that matches exactly the package structure of your API. Netbeans sets the default javadoc directory to $HOME/nbuser32/system/javadoc which then automatically gets added to the project's javadoc search path (see javadoc tab in explorer window). Netbeans also, by default will run applets in the appletviewer using an HTML file that has the exact name as the applet itself (equivalent to running the command: %>appletviewer http://localhost:8082/classpath/package/Applet.html) HOWEVER if the javadoc directory is located in default javadoc directory ($HOME/nbuser32/system/javadoc), then the internal webserver (running on port 8082) will locate and return the javadoc html document for that applet. The appletviewer will not find an applet tag in the file and will quietly exit without producing any output and the process will terminate and netbeans will not know that anything wrong happened (no error will be generated in the IDE.log file). To test to see if this is your problem, open a web browser and type the exact URL of the HTML file of your applet as produced by netbeans (check ide.log file for exact URL -- the line should look something like: [IDE-Exec] Executing: 0 .= C:\JDK1.3.0_02\JRE\..\bin\appletviewer 1 .= http://localhost:8082/classpath/package/Applet.html ) HOW TO RESOLVE THIS ISSUE: Move your javadoc directory to somewhere else other than to the nbuser32/system directory and remount the new path in your javadoc search path (javadoc tab in explorer window). Make sure you change the destination directory of future javadoc builds. To do this, 1) select Project->Settings... from the pull down menu 2) Expand the "Doclet" node. 3) Select the "Standard Doclet" leaf 4) Type, or browse to the new location of you javadoc files by selecting the "Destination" option.
Verified in NB3.3 beta 6.