Community
Participate
Working Groups
Build Identifier: 20100618-0524 Eclipse doesn't show Javadoc for org.w3c.dom.TypeInfo and org.w3c.dom.UserDataHandler classes and its methods, instead it shows "Note: This element neither has attached source nor attached Javadoc and hence no Javadoc could be found.", but I am sure everything is attached, because everything is OK for other classes in the same package. Moreover: for public static final fields Javadoc simply doesn't work (even message "Note: ..." is not getting shown). I tried to generalize this issue, but haven't found other classes with such issues, however I think they exist, because such selectiveness is very strange. Reproducible: Always Steps to Reproduce: 1. Attach rt sources 2. Go to org.w3c.dom.TypeInfo or org.w3c.dom.UserDataHandler class 3. Open Javadoc for class method or field.
Moving to JDT/UI for comment.
This works fine for me with JDK6 (1.6.0_20). When you open these types in Eclipse, do you see source or just the class file contents? Do you have the same problems in a new workspace in a new Java project?
(In reply to comment #2) > When you open these types in Eclipse, do you see source or just the class file > contents? I see the source (with Javadoc). > Do you have the same problems in a new workspace in a new Java project? I worked with a project in another working set of the same workspace today and the problem have disappeared. Now I cannot reproduce it. Btw, it is a bit unpredictable in context of which project RT sources are opened, maybe this fact created or hid the bug. Please don't close issue yet, maybe it will appear again. I'll try to reproduce it next two days, then I'll close it.
Today bug appeared again and I cannot understand the reason. It can somehow depend on the project in context of which these RT classes are used, but I don't see the relation yet.
Original issue was in build order. I have xmlbeans-2.3.0 without sources attached and this jar has several classes from org.w3c.dom package. So I have seen sources from one attachment and Javadoc was used from another attachment (nonexistent in this case). So this issue can be transformed to another one with such related points: 1) Order and export configuration doesn't influence "Link with Editor" button of Package explorer (and maybe other windows). 2) Sources and Javadoc are taken from different "attachments" even if only sources are specified. 3) As RT (and other system packages) are shared by all projects, "miss-ordered" RT in one project brings Javadoc problems to other projects where classes can be unambiguous. I think we should rename the issue to reflect new facts.
The root of these problems is bug 39468.
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.
