Hello,
some
of those incosistencies should be checked on activation of a process, and
therefore do not need to be signaled at runtime. If the error can happen because
of some XPath expression evaluated to the wrong value this static checking is
not possible, then a new exception should be thrown.
In
your case Chris, I think it is possible to check the existence of a
propertyAlias referenced from a correlation set definition (there is nothing
dynamic about that)
on
import and therefore "cannot happen" on execution.
Mit freundlichen Grüßen
Bernd
Eckenfels
Chief Architect
--
SEEBURGER
AG - Edisonstr.1 , D-75015 Bretten, Germany
Fax: +49 (0)7252 96-2400 - Phone:
+49 (0)7252 96-1256
mailto: - http://www.seeburger.de
-----Original Message-----
From: Chris Keller
[mailto:]
Sent: Tuesday, October
07, 2003 10:59 PM
To:
Subject:
[wsbpel] Should a correlationViolation be thrown when initiaing a correlation
set with missing property aliases
It is not clear in the current specification what
should happen if a property declared in a correlation set does not have a
corresponding property alias during initialization. For example if I have a property
called “purchaseOrderNumber” and create a
correlation set in my BPEL called “po” which
includes this property. If then
create a receive which initiates the correlation set “po” and uses a variable called “poVar” that is a associated with
a message called “poMessage”, but I neglect to
create a propertyAlias for “poMessage” to associate it with “purchaseOrderNumber”. My feeling is that this should throw a
correlationViolation (or some new fault like unknownPropertyAlias), but I couldn’t find it spelled out
anywhere.
Chris
