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.
| Summary: | Validation rule for message exchange - SA00060 | ||
|---|---|---|---|
| Product: | soa | Reporter: | Mikhail Kondratyev <mikk> |
| Component: | BPEL Validation | Assignee: | Vladimir Yaroslavskiy <yaroslavskiy> |
| Status: | RESOLVED FIXED | ||
| Severity: | blocker | ||
| Priority: | P4 | ||
| Version: | 5.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
| Attachments: |
rule61 sample
Test project |
||
|
Description
Mikhail Kondratyev
2006-08-30 08:44:34 UTC
Created attachment 33391 [details]
rule61 sample
This rule is not implemented. Since rule is not yet implemented, I am changing to enhancement. Rules implemented are marked with status 'Completed' here: http://enterprise.netbeans.org/specs/bpel/StaticAnalysisRules.html Very complicated for implementation rule. Knowing of previously executed activity is needed. So implementation should have some runtime logic for determining whether one activity precede other while execution. engine is not ready for message exchange Obsolete milestone, please reevaluate SA00060: The explicit use of messageExchange is needed only where the execution can result in multiple IMA-<reply> pairs (e.g. <receive>-<reply> pair) on the same partnerLink and operation being executed simultaneously. In these cases, the process definition MUST explicitly mark the pairing-up relationship. Created attachment 66806 [details]
Test project
fixed in soa-dev: 925498d31c71 |