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: | bpel validation wrt correlations | ||
---|---|---|---|
Product: | soa | Reporter: | kiran_bhumana <kiran_bhumana> |
Component: | BPEL Validation | Assignee: | Vladimir Yaroslavskiy <yaroslavskiy> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
kiran_bhumana
2006-11-28 04:30:15 UTC
According to Ron Ten Hov: If I understand your use-case correctly, it is possible to have a process that doesn't use correlation. If the process starts with a <receive> (and createInstance="yes"), it may never have another <receive> (or <onMessage>) that needs to be correlated to the instance. The example process given in section 5.1 of the specification shows such a process. Therefore, I am changing this issue status to invalid. This is not invalid. I am reopening this so i don't forget to do so later. If the email discussion says it is invlid, i will invalidate it. This is a bug that will help the users. This is neither difficult to implement nor something too complicated to understand. So i changed it to defect and to be fixed for NB 6.0. I might not hava chosen the milestone correctly, please correct it. the requirement is simple, for a receive that creates an instance, as shown in the bpel earlier, if a correlation tag is used, the only possible way to use the correlation is to initiate it. i.e. it should have been like the following. <receive name="Receive1" createInstance="yes" ...> <correlations> <correlation set="cSet1" initiate="yes"/> </correlations> </receive> For Sierra. Changed target milestone from Sierra to 6.1 in order to display correct info on NB 6.1 dashboard fixed. |