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 171462 - Bpel mapper is asynch after changing Wait Alarm Type
Summary: Bpel mapper is asynch after changing Wait Alarm Type
Status: VERIFIED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL Mapper (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P2 blocker (vote)
Assignee: Nikita Krjukov
URL:
Keywords:
: 174956 (view as bug list)
Depends on: 167105
Blocks:
  Show dependency tree
 
Reported: 2009-09-04 10:30 UTC by Vitaly Bychkov
Modified: 2009-12-04 08:22 UTC (History)
0 users

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 Vitaly Bychkov 2009-09-04 10:30:46 UTC 
The bpel Mapper becomes asynch after the wait Alarm Type changes.

Steps to reproduce: 
1. create Synchronous Sample and open Synchronous.bpel
2. add wait activity
3. select the wait activity and switch to the bpel mapper
4. See there is a Duration node in the right tree and Duration literal in the central panel
 joined to the Duration
5. switch to the Bpel Design and from property sheet change Alarm Type onto "Until"
6. back to the Bpel Mapper see there is the same state as was at 4th step

Workaround: to see the correct bpel mapper it is required to reopen the bpel file.


3. from the property editor change "Alarm Type" onto "Until"
4. select the wait activity and switch to the bpel mapper
5. Choose from Bpel Mapper Palette "Date & Time"/Deadline Literal
Comment 1 Nikita Krjukov 2009-10-21 15:47:35 UTC 
Fixed because of the issue #167105 is fixed
Comment 2 Nikita Krjukov 2009-10-26 21:58:26 UTC 
*** Issue 174956 has been marked as a duplicate of this issue. ***
Comment 3 Alexander Permyakov 2009-12-04 08:22:04 UTC 
verified