Meanings of the BPEL Standard Faults - Oracle SOA Suite 11g

Hi Folks.


Here are some so called 'BPEL Standard Faults' listed but without detailed information.
Oracle SOA SUite -Version 11.1.1.1.0 and later.

Fault name Description ambiguousReceive Thrown when a business process instance simultaneously enables two or more IMAs for the same partnerLink, portType, operation but different correlationSets, and the correlations of multiple of these activities match an incoming request message. completionConditionFailure Thrown if upon completion of a directly enclosed <scope> activity within <forEach> activity it can be determined that the completion condition can never be true. conflictingReceive Thrown when more than one inbound message activity is enabled simultaneously for the same partner link, port type, operation and correlation set(s). conflictingRequest Thrown when more than one inbound message activity is open for the same partner link, operation and message exchange. correlationViolation Thrown when the contents of the messages that are processed in an <invoke>, <receive>, <reply>, <onMessage>, or <onEvent> do not match specified correlation information. invalidBranchCondition Thrown if the integer value used in the <branches> completion condition of <forEach> is larger than the number of directly enclosed <scope> activities. invalidExpressionValue Thrown when an expression used within a WS-BPEL construct (except <assign>) returns an invalid value with respect to the expected XML Schema type. invalidVariables Thrown when an XML Schema validation (implicit or explicit) of a variable value fails. joinFailure Thrown when the join condition of an activity evaluates to false and the value of the suppressJoinFailure attribute is yes. mismatchedAssignmentFailure Thrown when incompatible types or incompatible XML infoset structure are encountered in an <assign> activity. missingReply Thrown when an inbound message activity has been executed, and the process instance or scope instance reaches the end of its execution without a corresponding <reply> activity having been executed. missingRequest Thrown when a <reply> activity cannot be associated with an open inbound message activity by matching the partner link, operation and message exchange tuple. scopeInitializationFailure Thrown if there is any problem creating any of the objects defined as part of scope initialization. This fault is always caught by the parent scope of the faulted scope. selectionFailure Thrown when a selection operation performed either in a function such as bpel:getVariableProperty, or in an assignment, encounters an error. subLanguageExecutionFault Thrown when the execution of an expression results in an unhandled fault in an expression language or query language. uninitializedPartnerRole Thrown when an <invoke> or <assign> activity references a partner link whose partnerRole endpoint reference is not initialized. uninitializedVariable Thrown when there is an attempt to access the value of an uninitialized variable or in the case of a message type variable one of its uninitialized parts. unsupportedReference Thrown when a WS-BPEL implementation fails to interpret the combination of the reference-scheme attribute and the content element OR just the content element alone. xsltInvalidSource Thrown when the transformation source provided in a bpel:doXslTransform function call was not legal (i.e., not an EII). xsltStylesheetNotFound Thrown when the named style sheet in a bpel:doXslTransform function call was not found.

Happy Learning...!!!!!!!!!!!! Fun Sharing.........!!!!!!!!!