This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 86949 - Moving elements from one diagram to another breaks diagrams
Summary: Moving elements from one diagram to another breaks diagrams
Status: VERIFIED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Alexey Anjeleevich
URL:
Keywords: UI
Depends on:
Blocks:
 
Reported: 2006-10-11 17:17 UTC by Andrey Yamkovoy
Modified: 2006-10-24 21:21 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrey Yamkovoy 2006-10-11 17:17:09 UTC
After moving some elements from one diagram to another diagrams shows 
incorrectly i.e. some elements can intersect each other or some part of diagram 
not shows at all and so on ... 


Steps to reproduce:
- Open 2 any bpel diagrams in design mode.
- Move window with one of them to another place to have both bpel diagrams 
visible at the same time.
- Move some bpel activities (or sequences) from one diagram to another and back.
- After some movings you will see that diagram become broken.
Comment 1 Michael Frisino 2006-10-12 06:57:43 UTC
This is unsupported functionality. Fix for this release ordinarily would be to
prevent such cross process DnD. Fix for next release would be to enable it.

For now, it is too late, we could document it as not-supported, and broken,
functionality.
Comment 2 Michael Frisino 2006-10-13 10:28:41 UTC
If this is not fixed we can doc it. However, Alexey has a fix, waiting for
review of Alexey's fix.
Comment 3 Alexey Anjeleevich 2006-10-13 11:52:49 UTC
Fixed in release55_dev branch
Fix: to class DnDHandler, method dragEnter(...) 4 lines added:

if (entity.getModel() != getDesignView().getBPELModel()) {
    dtde.rejectDrag();
    return;
}
Comment 4 Michael Frisino 2006-10-13 14:44:23 UTC

Reviewed and approved.

I think this change is very simple and very safe. It has been reviewed by
several people. Not many users will attempt this action, but when they do the
effect of this bug is quite severe. A recurring exception is displayd and the
target model is broken. I suggest we commit this fix to release55. It is simple
enough fix, that if there is regression it can be very easily rolled back. I
don't see any reason for regressions. The only area that should be thoroughly
checked is the DnD  of other artifacts ilke the WSDL and EJB service.
Comment 5 Alexey Anjeleevich 2006-10-13 15:48:09 UTC
Checked in release55 branch
Comment 6 Alexey Anjeleevich 2006-10-13 15:48:38 UTC
Fixed in both branches
Comment 7 Andrey Yamkovoy 2006-10-18 18:06:12 UTC
fixed