A DESCRIPTION OF THE REQUEST :
A problem arises when trying to execute a drag to the windows desktop or filesystem window. The current drop expects a List of java.io.File(s) that must already exist on the filesystem prior to the drop. This mechanism appears to be implemented to support file copying or moving from the current mounted filesystems only.
This is a problem when trying to implement something as simple as an FTP client application. The Client UI only contains a reference to a remote file that will need to be downloaded to the target location after the drop event. The file does not as yet exist locally so the drop can only contain an empty file
The enhancement would support a callback notification that occurs after the drop event has been completed. The callback would notify the listener that the drop completed and contain a java.io.File object indicating the location of the drop target in the mounted filesystems
JUSTIFICATION :
The current implementation does not provide a callback once the file has been dropped to the filesystem. This does not enable files to be dropped from a remote location other than those mounted to the local filesystem
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
A callback is needed indicating that the drop occurred to the filesystem. a handle (java.io.File object) to the filesystem location (drop parent directory) should be provided so that the subsequent callback method knows where to place the data to be dropped. this would enable the callback method to perform then stream the data to the desired directory
ACTUAL -
no appropriate mechansim as yet exists to perform this
CUSTOMER SUBMITTED WORKAROUND :
currently there is no known work-around short of employing a non-java mechanism