Please use the Apache issue tracking system for new NetBeans issues (https://issues.apache.org/jira/projects/NETBEANS0/issues) !!

Bug 79530

Summary: mapper isn't refreshed after adding a new element in .xsd file
Product: soa Reporter: _ hong_lin <hong_lin>
Component: BPEL MapperAssignee: Ed Wong <sunsoabi_edwong>
Status: VERIFIED FIXED QA Contact: issues <issues.netbeans.org>
Priority: P2    
Version: 5.x   
Target Milestone: 5.x   
Hardware: All   
OS: All   
Whiteboard: ENTPACK_55_BETA_RN 55EP_BETA_WAIVED
Issue Type: DEFECT Exception Report:
Attachments: mapper not refreshed snapshot
mapper refreshed after re-open IDE

Description _ hong_lin 2006-06-30 22:06:04 UTC
Build: NB 5.5 Dev (build 20060629200, Pack 2006.06.29)

To reproduce it:

1. Create a SynchronousSample sample project.
2. Open SynchronousSample.bpel and SynchronousSample.xsd in Editor Window.
3. Click the SynchronousSample.xsd in the Editor Widnow. In Schema view, click
the "Elements" item, then the "typeA" item in the right next column, then
"complexType", then "sequence". 
4. Right-click "sequence", select Add -> Element. Save the change.
5. Rename the new element to "paramB".
6. Click the SynchronousSample.bpel tab in the Editor Window. In the Design
view, click "assign" activity in the bpel diagram.
7. Open mapper window. Expand "inputVar -> inputType" and "outputVar ->
outputType" on both left side and right side.
==> new element "paramB" is not added under the inputType on both sides.
8. Close the mapper window and re-open it.
==> Get the same result as step 7.
(See the attached snapshot mapperNotRefreshed.png)

Workaround: Close the IDE and re-start it. (See the attached snapshot
mapperRefreshed.png)
Comment 1 _ hong_lin 2006-06-30 22:06:49 UTC
Created attachment 31562 [details]
mapper not refreshed snapshot
Comment 2 _ hong_lin 2006-06-30 22:07:18 UTC
Created attachment 31563 [details]
mapper refreshed after re-open IDE
Comment 3 Joshua Sandusky 2006-07-15 00:09:04 UTC
the mapper shows the change only when you switch out of the activity and then
back into it, which of course is not ideal. the mapper should automatically
update if at all possible without having to do this.
Comment 4 Ed Wong 2006-07-26 01:33:26 UTC
Assign to myself
Comment 5 Ritesh Adval 2006-09-22 01:01:35 UTC
This works for me. This used to be a problem pre windows group for mapper.
Marking as fixed.
Comment 6 skrishnan 2006-09-25 09:34:09 UTC
verified in build 060922.
By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo