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 179611

Summary:	Javadoc from JEE 6 is shown for a JEE 1.4 project
Product:	javaee	Reporter:	Tim Lebedkov <lebedkov>
Component:	Web Project	Assignee:	David Konecny <dkonecny>
Status:	RESOLVED WONTFIX
Severity:	normal	CC:	jlahoda, pjiricka
Priority:	P4
Version:	6.x
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:

Description Tim Lebedkov 2010-01-18 02:22:46 UTC

In an JEE 1.4 web project if I press Alt+F1 on the "getContextPath()" in the following line

servlet.getServletContext().getContextPath()

an URL from JEE 6 is shown:

http://127.0.0.1:8082/resource/jar:file:/C:/Program%2520Files/NetBeans%25206.8/enterprise6/docs/javaee6-doc-api.zip!/docs/api/javax/servlet/ServletContext.html#getContextPath%28%29

Comment 1 Jan Lahoda 2010-01-18 06:38:24 UTC

I would expect that Alt-F1 simply uses JavadocForBinaryQuery to find out which javadoc should be shown - this bug should belong to the code that provides the data for the query.

Comment 2 David Konecny 2010-01-24 14:49:59 UTC

The way this is currently implemented is that Java EE specification version is used to:
* list available application servers
* decide in which version misc deployment descriptor files (eg. web.xml) should be created
* decide which wizards should be available for project
* etc.
BUT Java API/Javadoc is offered based on project classpath regardless of Java EE specification version, that is if you create a project with specification version Java EE 1.4 and your application server is GlassFish V3 (==Java EE 6) then available Java API/Javadoc will be Java EE 6.

I agree that UI is misleading and should be improved to clearly communicate what Java EE spec versio is for. This is how it worked since NB4 though. If you really want to develop Java EE 1.4 app then I would suggest to use 1.4 EE server in your project.

Comment 3 Martin Balin 2016-07-07 08:53:43 UTC

This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue.

Thanks for your cooperation,
NetBeans IDE 8.2 Release Boss