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 78949 - can not use assignments in the if/else construct if used within a flow.
Summary: can not use assignments in the if/else construct if used within a flow.
Status: CLOSED WORKSFORME
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL Mapper (show other bugs)
Version: 5.x
Hardware: All Windows XP
: P2 blocker (vote)
Assignee: issues@soa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-23 00:40 UTC by bugbridge
Modified: 2006-07-25 22:48 UTC (History)
1 user (show)

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 bugbridge 2006-06-23 00:40:50 UTC
Steps to reproduce:

1.  Create the following business flow:
2.  Receive
3.  Flow1:  Branch1 has a regular assign.
4.  Flow1:  Branch2 has an if construct.
	Within the if construct, set if condition.
	Within the if construct, the "if" activity uses an assign, make a simple copy
	Within the if construct, the "else" condition uses an assign, make a simple copy

Result:
The last assign in the "else" condition does not generate any code.
Comment 1 Denis Anisimov 2006-06-23 06:42:54 UTC
I cannot reproduce this issue.
May be I don't understand correct steps for reproducing.
Could you please create more detail description of issue ?
What do you mean when you said "make a simple copy" ?
Comment 2 lchang 2006-06-26 22:48:16 UTC
Sorry for the vague description.

What is meant by "make a simple copy" is:
Prerequisite:  You have two variables created: variable1, variable2.
1.  Drag an Assign activity into the "if" construct
2.  Select the Assign activity, in the BPEL Mapper, copy from one variable to 
another (drag from variable1 to variable2)
3. Repeat the same for the "else" construct".  The else construct will not 
create the source for the copy statement.
Comment 3 Denis Anisimov 2006-06-27 09:34:37 UTC
It seems word "copy" here has relation to mapper.
So this is mapper bug I guess.
Comment 4 Joshua Sandusky 2006-07-14 23:58:22 UTC
just tested this, successfully generated the appropriate code inside an Assign
activity that resides inside an "else" of an "If" activity.
Comment 5 lchang 2006-07-25 22:48:39 UTC
cannot reproduce anymore as well.