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.
If the static evluation results in a possibility of multiple parallel for-each executions, then editor should throw an exception. Please see the email exchanges. ======== The best way to reason about parallel for-each is to transform it into an equivalent <flow> construct. In general, if the <receive>s use the same partnerLink, operation, and correlationSet(s), and they are concurrently active, a bpel:conflictingReceive must be thrown. You'd really have to work at it to avoid such an outcome in a parallel for-each with a <receive> inside. -Ron Kiran Bhumana wrote: Ron / Monica, If a BPEL for each defines a “Receive” and has ‘parallel=”yes” ‘ wouldn’t that cause a conflictingReceive fault? ===========
I meant, a validation "error" should be thrown when a receive is available in the for-each.
Need to check if this this one of the static analysis rules defined by the BPEL specification. Or if this is above and beyond that level of analysis. Not sure if you know, but, parallel=yes is not supported for ForEach in this release.
This is beyond the current static validations defined in the spec. Yes, i am aware that we are not supporting the parallel FOREACH.
I don't see this as being urgent for this rlease since the parallel=”yes” is not even supported by runtime. So there is certainly no need to push for integrtation of such fix before release.
Since there is no such rule in static analysis set of rules ( common static analiysis rules published by OMG ) I marked this is as enhancement. We have many rules from static analysis that is not yet implemented. All of them are enhancments. They needs to be implemented in next release. And one more. I don't understand EXACT situation when static analysis rule should detect error. I need exact and detailed description of this rule.
Created attachment 38261 [details] validation explanantion
accidentally created the attachment 90323 [details]-propAliasValidation.odt, it is for bug 90323. I can't delete the attachment once it is attached. Please ignore this attachment.
engine doesn't have parallel foreach
What will be implemented: if for-each has "parallel"=yes and <receive>s use the same partnerLink, operation, and correlationSet(s), error will be shown.
fixed in soa-dev: 26418f3aa4e8
Created attachment 67150 [details] Test project