JDK-4219342 : incomplete doc for java.awt.dnd.DragSourceDropEvent
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 1.2.1
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: solaris_2.5.1
  • CPU: sparc
  • Submitted: 1999-03-11
  • Updated: 2003-08-08
  • Resolved: 2003-08-08
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.
Other
5.0 tigerFixed
Related Reports
Relates :  
Description

Name: sdC67446			Date: 03/11/99


The doc for DragSourceDropEvent says nothing about the ctor's behavior
if input 'dsc' == null. Also the valid range for int parameter is
unspecified.

public DragSourceDropEvent(DragSourceContext dsc,
                           int action,
                           boolean success)

public DragSourceDropEvent(DragSourceContext dsc)

-------------
The doc says:
public DragSourceDropEvent(DragSourceContext dsc,
                           int action,
                           boolean success)

       Construct a DragSourceDropEvent for a drop, given the
       DragSourceContext, the drop action, and a boolean indicating if
       the drop was successful. 

       Parameters:
              dsc - the DragSourceContext associated with this
              DragSourceDropEvent 
              action - the drop action
              success - a boolean indicating if the drop was
              successful

________
======================================================================

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger FIXED IN: tiger INTEGRATED IN: tiger tiger-b15
14-06-2004

EVALUATION Name: agR10216 Date: 07/25/2003 This bug was fixed along with 4123385. ###@###.### 2003-07-25 ======================================================================
25-07-2003