JDK-6443651 : javadoc may need to be updated due to Mustang name change
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.rmi
  • Affected Version: 6
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2006-06-26
  • Updated: 2010-05-09
  • Resolved: 2006-07-22
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6
6 b93Fixed
Related Reports
Duplicate :  
Relates :  
Description
.
.
.
.
.
Due to Mustang name change (see http://javaweb.eng.sun.com/java/web/jdk/releases/mustang/FAQ.html
    for more info), the following javadoc needs to be updated:

(If below talks about trains earlier than Mustang, doesnt need to be changed.)

 ./java/rmi/server/SkeletonNotFoundException.html:118: not found.  Skeletons are not required in the Java 2 platform, so this exception is


 ./javax/rmi/CORBA/Util.html:460: <P>In Java 2 Platform, this method works as follows: 


 1 java/rmi/server/RemoteCall.java
     ...deprecated in the Java 2 platform since it is only
.
.
.
Ignore "." notes. I had to delete notes and replace them with "." s as cut-paste got messed up while filing.

Comments
EVALUATION This issue was already filed as 6425533, but I'll mark that CR as a duplicate of this one because this one lists an additional case (in java.rmi.server.RemoteCall) and also because this one might be more easily tracked among a group of recently filed CRs about the same issue in various categories. Note that the javax.rmi.CORBA.Util case is part of the RMI-IIOP API and thus belongs in a different CR, in the jets/idl product/category. Perhaps it should just be moved to 6443686? And yes, this needs to be fixed for Mustang.
27-06-2006