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.
This feels sort of broken, but I must admit I am not sure where the enhancement should be implemented to fix this. I installed NetBeans IDE 5.5 and then the Enterprise Pack 5.5. I chose to have the Enterprise Pack install SJS AS 9. That created an entry in the IDE's Server Manager for SJS AS 9. The Javadoc tab for that entry specifies the file F:\tools\windows\dev\netbeans\5.5\FCS\enterprise3\docs\javaee5-doc-api.zip. This is all fine and well, but I cannot access those javadocs. Here's what I did to try: 1. Create a standard EE 5 web application, specifying SJS AS 9 as the server. 2. In a class within that web application, import javax.jws.soap.SOAPBinding; 3. In the IDE's editor right-click on SOAPBinding and choose Show Javadoc. I get the standard error message at the bottom of the editor: "Javadoc not found. Use the Library Manager to specify Javadoc for classpath items..." This is because while the Server Manager has the correct entry for the javadoc .zip file, the IDE's project system knows nothing about that .zip file. To verify this, I expanded the Libraries node for the project. If I right-click any of the .jar files under JDK 1.5 the "Show Javadoc" context menu entry is enabled. For the .jar files under the SJS AS entry, that context menu entry is always disabled. And that's a bummer, because it makes the out-of-box experience a bit unfriendly. If I go to the Library Manager and add a new library (I called it "EE5") so that I can associate F:\tools\windows\dev\netbeans\5.5\FCS\enterprise3\docs\javaee5-doc-api.zip with F:/tools/windows/dev/sjsas/9.0/fromNBEntPack55FCS/lib/javaee.jar then I can get access to the Javadocs from within the IDE's editor. Is there any way this library entry could be setup automatically? Could the server plugin somehow verify that the server's .jar files are associated with a javadoc .zip file? That seems clumsy, but as I said, the current situation is less than ideal....
This is a bug...Otherwise, what's the heck we added this javadoc in the IDE distro... I'll take a look, and see what can be done...
this should get assigned to someone that is actively working on the plugin
*** Issue 110194 has been marked as a duplicate of this issue. ***
this appears to have been fixed. At step 3, I see the javadoc for SOAPBinding.
Works for me too, using NB 6 Beta2.