Bug 215320 - Javadoc contents retrieval doesn't support proxy connections
Summary: Javadoc contents retrieval doesn't support proxy connections
Status: VERIFIED DUPLICATE of bug 136091
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.3.1   Edit
Hardware: PC Windows 2000
: P3 major (vote)
Target Milestone: 3.7 M5   Edit
Assignee: Ayushman Jain CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 287145 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-01-15 04:49 EST by Maxx L. CLA
Modified: 2011-03-07 11:07 EST (History)
6 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maxx L. CLA 2008-01-15 04:49:56 EST
Build ID: M20071023-1652

Steps To Reproduce:
Required: BEA WLS Tools 1.1.1 (Plugin for Eclipse)
get it here: https://dev2devclub.bea.com/updates/wls-tools/
+ see details below

1. Have a WebLogic 9.2 (MP1) Server runtime properly configured in your Eclipse, to be used in an EJB Project.
2. Create a new EJB Project (using the default settings).
3. Create a new class, whatever you called it.
4. In the constructor, in a method or in a static context, type the word "Session" (First-Letter case!!!) and wait for the content-assist drop-down list.
5. You have an "Internal Error" logged into your Eclipse "Error Log" tab (see details below).
6. The Javadoc is unavailable for such classes (due the error while retriving(?) the Javadoc).

More information:
Details about the logged error:
-------------------------------

Severity: Error

Message: Internal Error

Exception Stack Trace:

Java Model Exception: Java Model Status [Unknown javadoc format for Session [in Session.class [in javax.jms [in C:\bea2\weblogic92\server\lib\api.jar]]]]
	at org.eclipse.jdt.internal.core.BinaryType.getAttachedJavadoc(BinaryType.java:975)
	at org.eclipse.jdt.internal.ui.text.java.ProposalInfo.getHTMLContentReader(ProposalInfo.java:112)
	at org.eclipse.jdt.internal.ui.text.java.ProposalInfo.extractJavadoc(ProposalInfo.java:99)
	at org.eclipse.jdt.internal.ui.text.java.ProposalInfo.computeInfo(ProposalInfo.java:76)
	at org.eclipse.jdt.internal.ui.text.java.ProposalInfo.getInfo(ProposalInfo.java:59)
	at org.eclipse.jdt.internal.ui.text.java.AbstractJavaCompletionProposal.getAdditionalProposalInfo(AbstractJavaCompletionProposal.java:521)
	at org.eclipse.jface.text.contentassist.AdditionalInfoController$3.run(AdditionalInfoController.java:102)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Session data:

eclipse.buildId=M20071023-1652
java.version=1.5.0_14
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en
Command-line arguments:  -os win32 -ws win32 -arch x86
-------------------------------

Note: included related plugin is BEA WebLogic Server Tools 1.1.1.200711270600 (see above url to download it)

In my project ("EJB" > "EJB Project") is included the "WebLogic System Libraries" container, containing the following libs coming from the WLS install:
  C:\bea2\weblogic92\server\lib\api.jar
  C:\bea2\weblogic92\server\lib\wls-api.jar

If I right-click on the container, then "Configure..." and selecting each lib one by one, the attached Javadoc URL's are:
  api.jar = http://java.sun.com/j2ee/1.4/docs/api
  wls-api.jar = http://edocs.bea.com/wls/docs92/javadocs
which seems both to be fine.

The problem could be I have no internet connection, but I effectively DO HAVE the internet connection open (even it's through a Proxy, I opened the internal Eclipse web browser to test/"initialize" it - such things works when downloading files used in validation process, such as DTD's or XSD's).
Comment 1 Dani Megert CLA 2008-01-15 08:34:07 EST
Either the Javadoc itself is broken or JDT Core accidentally treats this as being invalid. Moving to JDT Core for comment.
Comment 2 Jerome Lanneluc CLA 2008-02-06 05:19:03 EST
The Javadoc for javax.jms.Session seems to have an unknown format. How can we get access to it ?
Comment 3 Olivier Thomann CLA 2008-03-12 10:04:34 EDT
Can you test the same tests case without using a proxy ? This might be the problem here.
Comment 4 Maxx L. CLA 2008-03-12 10:35:19 EDT
Unfortunately, no.
Comment 5 Olivier Thomann CLA 2008-03-12 10:50:13 EDT
Then can you try to install your javadoc locally and point to the local javadoc instead?
Comment 6 Maxx L. CLA 2008-03-12 12:32:24 EDT
OK then...

J2EE 1.4 API Doc download:
http://java.sun.com/j2ee/1.4/download.html#apidocs
=> "Platform API Docs"
j2eeri-1_4-doc-api.zip download (3.38 MB)

Put/copied it into C:\Java\j2eeri-1_4-doc-api.zip (*)

Then back to the Container (see above) config, I changed the doc location to:
-> Javadoc in archive
  -> External file
  + archive path = (path (*) above)
  + path within archive = clicked on "Browse..." + selected "apidocs"

Now while re-testing steps I described previously above, the errors do not show anymore in the Eclipse Error Log tab.
+ the Javadoc displays fine...
Comment 7 Olivier Thomann CLA 2008-03-12 12:55:36 EDT
So the problem comes from the proxy settings.
Updating title accordingly.
Comment 8 Markus Keller CLA 2009-08-20 05:36:50 EDT
*** Bug 287145 has been marked as a duplicate of this bug. ***
Comment 9 Markus Keller CLA 2009-08-20 05:51:25 EDT
Sounds the same as bug 136091. Platform Proxy settings have been introduced with bug 154100.
Comment 10 Daniel Hirscher CLA 2009-08-21 02:34:43 EDT
Please note that bug 287145 is not an exact duplicate of this one.
I do not get entries in the error log. I get a proxy authentication dialog.

Please see as well bug 286631 for a fix for the URLConnection to be able to connect through the proxy using the authentication details configured in the platform preferences.

Thank you.
Comment 11 Olivier Thomann CLA 2011-02-25 13:40:20 EST
Ayushman, I think proxy settings are now used for javadoc retrieval.
Please close if this is the case.
Comment 12 Ayushman Jain CLA 2011-02-28 04:12:35 EST
(In reply to comment #11)
> Ayushman, I think proxy settings are now used for javadoc retrieval.
> Please close if this is the case.

Yup. Proxy settings are now supported platform-wide. Any problems in fetching javadoc because of timing out will be caught with a separate error msg introduced with the fix for bug 136091.

*** This bug has been marked as a duplicate of bug 136091 ***
Comment 13 Olivier Thomann CLA 2011-03-07 11:07:45 EST
Verified for 3.7M6.