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 83632 - Validation needed for variable use in flow structure
Summary: Validation needed for variable use in flow structure
Status: RESOLVED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL Validation (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Vladimir Yaroslavskiy
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-28 23:41 UTC by lchang
Modified: 2008-05-23 14:50 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
bpel and wsdl files (12.30 KB, application/octet-stream)
2006-08-28 23:55 UTC, lchang 		Details
Test project (6.80 KB, application/x-compressed)
2008-05-23 14:49 UTC, Vladimir Yaroslavskiy 		Details
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 lchang 2006-08-28 23:41:15 UTC 
The absence of the run-time support for the <link> construct for <flow> causes 
a conflict of using one variable in two or more concurrent flow branches.

In the process of helping users to create valid BPELs we need validation to 
inform the user that they can't use one variable in concurrent flow branches.
Comment 1 lchang 2006-08-28 23:53:00 UTC 
See attached project.  This project in most cases will pass.  However, on 
occasion, if both assign activities in each branch tries to write to the same 
variable at the exact same time there will be a failure.
Comment 2 lchang 2006-08-28 23:55:03 UTC 
Created attachment 33338 [details]
bpel and wsdl files
Comment 3 Denis Anisimov 2006-08-29 11:51:28 UTC 
I understand your concern here.

But described situation could appear even if "link" will be availible 
in editor. So what BPEL specification tell about this ?
Please let me know if you have pointer to specification where described situation 
appears and discussed.

Since this situation could appear in any BPEL file specification should deny
such construction explicitly if it is really is not allowed.
Otherwise this is correct construction and runtime should care about this.
If runtime cannot care appropriately then this is runtime problem.

I need exact situation when copying in the same variable is not allowed if any.
With such description I can write validation rule.
Comment 4 lchang 2006-08-29 21:36:25 UTC 
Comment from Murali:

Same variable is used in more than one FLOW branch in “to” construct 
of “Assignment” activity might lead to unpredictable result. Result would 
depend on order of execution of activities in FLOW branches. 

When there is support for "link" user would be able to control the execution 
of activities in FLOW branches.

When user is not using "link" (absence of link) or link not used in 
appropriately may result unpredictable value for a variable, system should 
warn user on this situation.

Including Ron and Monica.

Ron/Monica:
What are your thoughts on this? Is there a reason why this does not show up in 
static analysis?
Comment 5 Jiri Prox 2007-09-17 20:26:48 UTC 
Obsolete milestone, please reevaluate
Comment 6 Vladimir Yaroslavskiy 2008-02-27 15:02:27 UTC 
fixed.
Comment 7 Vladimir Yaroslavskiy 2008-02-27 15:03:54 UTC 
reopen, close by mistake
Comment 8 Sergey Lunegov 2008-05-05 08:43:32 UTC 
Vladimir, please take this one into account.
Comment 9 Vladimir Yaroslavskiy 2008-05-23 14:49:58 UTC 
Created attachment 61836 [details]
Test project
Comment 10 Vladimir Yaroslavskiy 2008-05-23 14:50:41 UTC 
fixed: 9ef0c86ffe91