Re: [wsbpel] Issue - 219 - proposal to vote

["Yaron Y. Goland" <ygoland@bea.com>]

I am uncomfortable with the idea of obscuring a language fault with a 
correlation violation. The underlying fault is a language fault and for 
debugging and other purposes that is the fault that the programmer needs 
to address. As such I believe we should stick with a language fault in 
the case that a correlation set can't be initiated due to a language error.

In general having a single fault that can cover multiple different fault 
conditions isn't a great idea. It significantly reduces the value of the 
fault because the programmer can't be sure what the real issue is.

	Yaron

Alex Yiu wrote:
> 
> 
> -----------------------------------------------------------
> In section "10.2 Defining and Using Correlation Sets"
> 
> After the pargraph beginning with "If multiple correlation sets are used
> in a message activity", add a paragraph:
> 
> "If an error occurs during executing a propertyAlias used by a
> correlation set in a message activity, correlationViolation fault MUST
> be thrown, instead of underlying query language related fault (e.g.
> selectionFailure)."
> 
> Enrich the description of "correlationViolation" fault in Appendix A:
> 
> FROM:
> "Thrown when the contents of the messages that are processed in an
> invoke, receive, or reply activity do not match specified correlation
> information. "
> 
> TO:
> "Thrown when the contents of the messages that are processed in an
> invoke, receive, or reply activity do not match specified correlation
> information OR when the initiate attribute do not match the state of the
> correlation information OR when a corresponding propertyAlias fails to
> execute"
> 
> -----------------------------------------------------------
> 
> 
> Regards,
> Alex Yiu
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your TCs in 
> OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>