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 81404 - BPEL Project validation fails to catch two reply activities for the same partner
Summary: BPEL Project validation fails to catch two reply activities for the same partner
Status: RESOLVED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL Validation (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Vladimir Yaroslavskiy
URL:
Keywords:
Depends on:
Blocks: 89926
  Show dependency tree
 
Reported: 2006-07-29 01:57 UTC by malkit
Modified: 2007-10-12 10:19 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
WSDL File (2.19 KB, application/octet-stream)
2006-07-29 01:58 UTC, malkit 		Details
BPEL File (2.58 KB, text/html)
2006-07-29 01:58 UTC, malkit 		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 malkit 2006-07-29 01:57:14 UTC 
The attached bpel contains two reply activites for the same partner but the bpel
validation fails to catch that. Also note that these reply activities are not
part of any if/switch or any other branch on a decision gate.
Comment 1 malkit 2006-07-29 01:58:12 UTC 
Created attachment 32331 [details]
WSDL File
Comment 2 malkit 2006-07-29 01:58:46 UTC 
Created attachment 32332 [details]
BPEL File
Comment 3 Michael Frisino 2006-07-30 18:14:52 UTC 
are you aware of a particular static analysis rule that pertains to this case?
We have not implemnted all of the 90 rules because of time constraints.

Or was this one of the cases comvered by the previous build system validation
logic that has now been displaced by common validation logic?
Comment 4 malkit 2006-07-31 19:35:02 UTC 
Standard faluts section of spec talks about missingRequest fault type to be 
Thrown when a reply activity cannot be associated with an incomplete receive 
activity by matching the partnerLink, operation and messageExchange tuple.

Although not defined as part of static validation, this should be part of 
validation. Although, agreed the validation cannot fully validate multiple 
reply for all cases, for instance if they happen to be part of any if activity 
based on condition outcome of which is determined in runtime, but for other 
simpler cases (like the one attached), the validation should be able to catch 
and report this to be invalid.
Comment 5 Praveen Savur 2006-07-31 20:09:30 UTC 
 There are many validation rules that can be implemented that are not defined by
Static Analysis.  

So it would be better to change this to an Enhancement rather than a bug.
Comment 6 Ritesh Adval 2006-09-06 01:48:34 UTC 
bpel validation bug, changing subcomponent.

Should we have a subcomponent called "validation"?
Comment 7 Michael Frisino 2006-11-13 12:07:27 UTC 
need to make sure this is reasonable RFE.
Comment 8 Sergey Lunegov 2007-02-05 10:13:26 UTC 
future release.
Comment 9 Vladimir Yaroslavskiy 2007-10-11 14:23:50 UTC 
Fixed in trunk and sierra.
Comment 10 Vladimir Yaroslavskiy 2007-10-12 10:09:22 UTC 
Correction: fixed in sierra only.
Comment 11 Vladimir Yaroslavskiy 2007-10-12 10:19:38 UTC 
The algorithm for the rule is:

1. If two replies for the same partner link are not in a decision gate (if, else, elseif, FaultHandlers),
   the error is shown.

2. If two replies for the same partner link have common grandparent (Sequence) and all subparents are Sequence,
   the error is shown even the replies is in a decision gate.