Community
Participate
Working Groups
- install a JRE 1.4.1 - enable use of JRE containers - create a Java project -> JRE container is on the class path -> the jsse jat does not have a source attachement - Create a zip containing the package javax.net and the java files for each of the class files that are in the same package as in the jsse jar. - attach it as source to jsse.jar -> no effect, source is still not found for these classes Is this on purpose?
None of the .class files contained in jsse.jar has its source in src.zip which is contained in the JDK1.4.1 install dir. I don't see how we could find a source in this case. Do you have the source of these classes?
Could you please send me the source you used for the second part of the steps to reproduce? Because in my JDK1.4.1 installation, I don't have the source for the classes inside jsse.jar.
For clarification: - intially not having any source attachment is the expected behavior - the source zip I attached is a fake and it is, as described, incomplete as it contains a single package only.
We retrieve the source according to the source attribute when one is available. If I take the example of the javax.net.DefaultServerSocketFactory.class. The source attribute is DashoA6275. So if you want the source to be retrieve, you should create a zip file which contains a file called javax.net.DashoA6275. And in this file you can define the 4 classes. Then the source is mapped properly. I don't see why we would try to infer the source name if there is a source attribute. If you absolutely want a source to be attached, follow the source attribute name and everything will work fine. Ok to close?
Closing. This is not a bug. The source attribute is completely different from the class name. If the right file name is used to create fake source, the source attachement works fine. Reopen if you believe this is still a bug.
