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.

Bug 191043 - Fiddling with "Cannot perform Show Javadoc here" problem
Summary: Fiddling with "Cannot perform Show Javadoc here" problem
Status: CLOSED WORKSFORME
Alias: None
Product: javaee
Classification: Unclassified
Component: Web Project (show other bugs)
Version: 6.x
Hardware: PC Other
: P3 normal (vote)
Assignee: David Konecny
URL:
Keywords:
Depends on:
Blocks: 189185
  Show dependency tree
 
Reported: 2010-10-15 21:55 UTC by gliesian
Modified: 2014-04-23 17:14 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description gliesian 2010-10-15 21:55:11 UTC
Fiddling with "Cannot perform Show Javadoc here" problem:
http://forums.netbeans.org/ptopic23262.html
Comment 1 Jan Becicka 2010-10-21 08:30:14 UTC
copy paste from http://forums.netbeans.org/ptopic23262.html
-----
After playing around with this a bit here are some observations - and a questionable work-around for EE projects. 

1 - The javadoc Index Search (shift-f1) will find the javadocs for any library defined anywhere in the Library Manager. But this does not make a javadoc available via ctrl-space, alt-f1, etc. 

2 - The only way to get javadoc via the alt-f1, ctrl-space, or the window/other/javadoc window is to have the appropriate library (with its associated javadoc) attached to your *project*. Just adding javadoc's via the library manager or platform manager has no effect until the library is added at the project level. 

For example, looking at the Project/Libraries node for an SE project shows the JDK/SE platform. If it has javadocs defined via the Library Manager, then alt-f1 will work. 

3 - Alt-f1 javadocs for EE libraries within EE projects is broken. For an Enterprise project the Project/Libraries node will show the standard JDK/SE platform and a server platform (Glassfish in my case). Alt-f1 won't work for any EE libraries (including JSF, CDI, EJB, etc.) even though the server libraries are listed under the Glassfish library node and are defined via the Library Manager with associated javadocs. 

4 - There is a work-around for #3 above. Add the "Java EE 6 API Library" to the project (via Library Manager). 

With #4 do you have the same libraries/classes defined twice on the classpath? This doesn't seem like a real good idea. 

Maybe one of the Netbeans Team will step forward and clarify this? Is there a bug with alt-f1 and server libraries?
-----

Show javadoc implemented in java/editor. CCing Jesse, who did recent changes in Javadoc support.
Comment 2 Jesse Glick 2010-10-21 13:50:34 UTC
My changes were just to support HTTP URLs; I doubt they have anything to do with this. #3 sounds like a simple bug in some EE-specific JavadocForBinaryQueryImplementation.
Comment 3 David Konecny 2010-10-22 09:12:48 UTC
#3 works fine for me on NB 6.9.1. And I would expect it to just work. When an IDE is started with empty userdir and GlassFish server is registered in the IDE then server library is automatically created - have a look at Tools->Libraries->ServerLibraries: GlassFish library should be there and in its Javadoc panel it should have Java EE 6 doc api jar.
Comment 4 jbfaden 2014-04-23 17:14:22 UTC
Why is there a "Show Javadoc" item on the Java editor pane popup menu (right-click), when I always get "Cannot perform Show Javadoc here"?  Either this function should be restored or it should be removed from the popup menu.