java.lang.NoSuchMethodError: createImageUsingNativeSize error in 1.8.0_45

[Alexander Scherbatiy]

   It looks like known issue JDK-8077016 [macosx] Image transfer through 
System Clipboard is broken in 1.8.0_40 on Mac OS X
     https://bugs.openjdk.java.net/browse/JDK-8077016

   Thanks,
   Alexandr.

On 7/23/2015 2:32 PM, Alexander Scherbatiy wrote:
>
>  Could you file an issue on it: http://bugreport.java.com/bugreport
>
>  Thanks,
>  Alexandr.
>
> On 7/23/2015 2:27 PM, Paul Taylor wrote:
>> On 23/07/2015 11:19, Paul Taylor wrote:
>>> This code that was used in some circumstances for dealing with 
>>> single images dragged and drop from certain webbrowsers (firefox) 
>>> gave no issues in 1.8.0_25
>>>
>>>     image  = (Image) 
>>> trans.getTransferData("image/x-java-image;class=java.awt.Image");
>>>
>>> but now in 1.8.0_45 causing
>>>
>>> java.lang.NoSuchMethodError: createImageUsingNativeSize
>>> at sun.lwawt.macosx.CDataTransferer.getImageForByteStream(Native 
>>> Method)
>>> at 
>>> sun.lwawt.macosx.CDataTransferer.platformImageBytesToImage(CDataTransferer.java:238)
>>> at 
>>> sun.awt.datatransfer.DataTransferer.translateBytes(DataTransferer.java:1659)
>>> at 
>>> sun.lwawt.macosx.CDataTransferer.translateBytes(CDataTransferer.java:142)
>>> at 
>>> sun.awt.dnd.SunDropTargetContextPeer.getTransferData(SunDropTargetContextPeer.java:269)
>>> at 
>>> sun.awt.datatransfer.TransferableProxy.getTransferData(TransferableProxy.java:73)
>>> at 
>>> java.awt.dnd.DropTargetContext$TransferableProxy.getTransferData(DropTargetContext.java:376)
>>> at 
>>> com.jthink.jaikoz.draganddrop.ImageHandler.createImageCell(ImageHandler.java:30)
>>>
>>> Is this a bug in the new version of OSX Java or am I simply doing 
>>> something wrong, is there a simple workaround ?
>>>
>>> Paul
>>>
>>>
>>>
>> It seems to be 
>> https://bugs.openjdk.java.net/browse/JDK-8077016?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#issue-tabs 
>> but breaking use of the clipboard for copy and pate of images is a 
>> massive bug dont you think, surely this should be a priority 1 bug as 
>> we are not talking about some obscure functionality here ?
>>
>> Paul
>>
>>
>