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 82094 - Undo after change the order of ElseIf sections renames the If activity
Summary: Undo after change the order of ElseIf sections renames the If activity
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 Yarmolenko
URL:
Keywords: REGRESSION
Depends on: 81709
Blocks:
  Show dependency tree
 
Reported: 2006-08-07 18:16 UTC by Andrey Yamkovoy
Modified: 2006-09-05 11:40 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrey Yamkovoy 2006-08-07 18:16:24 UTC 
It's need to invoke 2 undo action after change the order of ElseIf sections to 
undo the changes correcly.

Steps to reproduce:
- Create Synchronous sample project.
- Add 'If' activity to process.
- Add 2 'ElseIf' sections to 'If' activity with Empty elements.
- Change the order of these 'ElseIf' sections by drag-n-drop on diagram.
- Invoke Undo action (shortcut Ctrl + Z).
- Notice that name of 'If' activity was changed.
Comment 1 Alexey Yarmolenko 2006-08-18 10:24:41 UTC 
Renaming If element is a woraround for IZ81709. Need to fix 81709 on OM side 
first.
Comment 2 Denis Anisimov 2006-08-21 13:14:11 UTC 
Please don't create more problems than already exist.
This bug with its description is not mine.
This is problem in UI part.

First of all I beleive it could be fixed in UI part. You need to place your 
various actions that you used in hack in one transaction. In this case
undo will turn back transaction as a whole and all will be OK.

Anyway - there is a hack. It should be removed. 
Issue is caused by hack. 
This bug will disappear after removing hack. 
Bug IZ81709 is absolutely other problem that needs to be fixed.
Comment 3 Michael Frisino 2006-08-22 16:09:07 UTC 
Denis, what is your preference? Do you want us to reopen bug 81709? Currently
81709 is closed as fixed, but that is only because of hack. Do you want us to
reopen 81709 and have you fix it in OM.
Comment 4 Michael Frisino 2006-08-22 16:12:43 UTC 
reassigning to Alexey to work out with Denis relationship b/t this bug and
81079, since Alexey A is on vacation.
Comment 5 Denis Anisimov 2006-08-22 16:24:06 UTC 
Yes , pointed bug should be reopened.
This is bug in XAM/XDM and it should be fixed by XML team.
If fix is recognized as hack by developer himself then I beleive we SHOULD
remove it from code.
This was acceptable ONLY for Beta.
Comment 6 Michael Frisino 2006-08-22 16:50:35 UTC 
Is there a way for XML team to see the bug without us undoing the hack in bug
81709? Or do we need to undo the hack in order to help the XML team reproduce
the bug?
Comment 7 Alexey Yarmolenko 2006-08-28 19:59:10 UTC 
I see this bug fixed already. 

Renaming the If activity was a kind of workaround for bug in OM and this 
workaround was implemented only in cokebeta branch, while the OM bug is 
already fixed in trunk.
Comment 8 Andrey Yamkovoy 2006-09-05 11:40:27 UTC 
fixed