Community
Participate
Working Groups
Eclipse 3.4.1 M20080911-1700 Go To Window->Preference->Java-Editor-Content Assits->Advanced and select only Other Java Proposals and Type Proposals. Go an configure proxy setting in Windows->Preference. This problem happens only if proxy is configured. Create a new ejb project and a bean. Go to the class of the bean, type @Re and Ctrl+Space. The following error occurs. Java Model Exception: Java Model Status [Cannot retrieve the attached javadoc for ] at org.eclipse.jdt.internal.core.JavaElement.getLibraryJavadocLocation(JavaElement.java:704) at org.eclipse.jdt.internal.core.JavaElement.getJavadocBaseLocation(JavaElement.java:661) at org.eclipse.jdt.internal.core.BinaryType.getJavadocContents(BinaryType.java:1030) at org.eclipse.jdt.internal.core.BinaryType.getAttachedJavadoc(BinaryType.java:971) at org.eclipse.jdt.internal.ui.text.javadoc.JavadocContentAccess2.getHTMLContent(JavadocContentAccess2.java:98) at org.eclipse.jdt.internal.ui.text.java.ProposalInfo.extractJavadoc(ProposalInfo.java:96) 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:510) at org.eclipse.jface.text.contentassist.AdditionalInfoController$3.run(AdditionalInfoController.java:105) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) This error happens in an internal product. The class path of the project contains our adopter jars. I suppose one of the jars (the one containing @Remote annotation) is corrupt or something. It would be great if this information is given in the JavaModelStatus. Which is the jar in problem.
If the problem only occurs with proxies, then it has nothing to do with the jars. The problem must come from the connection to the javadoc location itself. There are known issues with proxies.
(In reply to comment #1) > If the problem only occurs with proxies, then it has nothing to do with the > jars. The problem must come from the connection to the javadoc location itself. > There are known issues with proxies. > Yes, I was able to reproduce this problem only with proxy configured.
Then closing as a dup of bug 136091. I had no time to assess the proxy support from the platform. *** This bug has been marked as a duplicate of bug 136091 ***
(In reply to comment #3) > Then closing as a dup of bug 136091. > I had no time to assess the proxy support from the platform. > > *** This bug has been marked as a duplicate of bug 136091 *** I dont think this is really a duplicate. What the user is really asking here is that we should be able to explicitly report which jar's javadoc URL is corrupt. On the other hand bug 136901 deals with a hang due to delay in fetching javadoc, even though the path may be correct.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
