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 not set attribute 'parallel' in forEach activity then compiler fails with message: Error: cvc-complex-type.4: Attribute 'parallel' must appear on element 'forEach'. If set this attribute then validator fails with message: Attribute "parallel" is not supported in this release of the BPEL SE.You cannot deploy process containing this attribute.
Hmm, What is situation here? <attribute name="parallel" type="bpws:tBoolean" use="required"/> Attrbute is required by schema but not supported by runtime. Denis do we have other case like this? We should solve in consistent way. Also this attribute should not be shown in property sheet at all, since it is out of scope for 5.5. Nikita please remove.
I don't understand actually what I need to do. There is misunderstanding between us and Alaska runtime. I have schema file from them where this is attribute is commented out. So this means that they don't support this attribute. This is implemented in validation rule. But another validation ( I mean here build-time validation ) said that this attribute should be set. That's correct from schema point of view, because it is required. So possibly Alaska mean that this attribute should be always set to some value. WHAT value ? I don't know. Schema that they point to me dosn't contain any mentions about it. >Denis do we have other case like this? We should solve in consistent way. If you mean - are there more attributes that are required but they are not supported by runtime then answer - no. But I believe this is question not for me. This is not first problem that we found with misunderstanding between validation (design guidance) and runtime validation. I think this is consequence of bad "documentation" that we have from Alaska team . This documentation is just schema file and it is not sufficient. As consequence we have problem with understanding: 1) what we need to do with not supported attribute ? ( if it have default value then should we allow it ?) - we still don't have answer to this question. 2) what we need to do with attribute that required , but not suported and there is no default vakue ( this is matter of current issue ). 3) some elements are not marked in schema as not supported ( f.e. compensateScope ). I just want to sya that we need from Alaska much more information then we have now.
My proposal is as follows: It seems to me that one solution is that IDE should require presence of attribute but only allow the value of attribute to = false. This would require slight change in validation rule for "runtime not supported" validation. To implement such logic requires: IDE should adjust new For Each elements to explicitly set the paraellel attribute = "false". Validation system should change runtime validation rule to: if attribute "parallel" value = true return "Error : Parallel processing of For Each element is not supported by runtime. Please change this value to "false". This would allow both validators to succeed. Are there any other suggestions that could solve this issue?
Denis, can you execute on my suggestion? The runtime team agrees that it will not be a problem for the attribute to be present provided its value is "false".
Fixed. Consider attribute value "no" as allowed by runtime. Validation ( I mean here runtime validation) will fail only when attribute is set to "yes".
verified: - attribute removed from properties - default value is 'no' - validator post warning if value is 'yes'