We ran into a problem of stackoverflow exception inside JGOView dragSetData when it’s trying to do writeObject to an outputstream.<?:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />
Here is what happened. We have an application that allows user to draw their workflow diagram which uses JGO SWT 5.1. When an user creates a graph with more than 800 elements (node, route/link, branches, etc), and he tries to drag one of the node to a different position on the canvas, the mouse down event is captured, followed by drag enter, drag move, etc, then when it got to dragSetData, an stackflow overflow exception happens. This looks like it has something to do with the failure of object serialization during DND. The end result is after exception happens, all the other mouse events that are supposed to happen are discarded (for example mouse up, etc), then the application is in a weired stated and seems to be stucked in mouse down => drag state. If I reduced the graph elements to about 400-500, the application works correctly.
Here are my questions:
1) any body runs into similar situation before, and how they fix it?
2) does increasing the stack size for Java –Xss flag help in this case (how big should it be??)
3) why does mouse move event in JGO results calling internal / native DND which is perform the serialization
Any help will be appreciated. Thanks.