The BPEL Interpreter catalog contains messages in the range
BEA2031650 - BEA2031699. Messages in this catalog are part of the
com.bea.bpel.interpreter.internal.expression.messages Internationalization package and the
com.bea.bpel.interpreter.internal.expression.messages Localization package.
|
BEA-2031650
|
Error: No value found for variable 'variable' and property 'property'.
|
Description
| The variable value does not contain the specified property. |
|
Action
| Ensure that the variable does contain the specified property. |
|
|
BEA-2031651
|
Error: A selection operation returned a nil XML.
|
Description
| The expression evaluated to an XML object specified as a nil value. |
|
Action
| Ensure that the expression evaluates to a non-nil value. |
|
|
BEA-2031652
|
Error: Expression 'expression' returned noItems items when exactly 1 is required.
|
Description
| Expressions (particularly those used in Copy) should return a single item. If the expression evaluates to 0 or more than 1 item it is an exception. |
|
Action
| Ensure that the expression selects a single item. |
|
|
BEA-2031653
|
Error: Scripting language 'scriptingLanguageURI' is not supported.
|
Description
| The scripting language is not supported. This should be caught by validation during deployment. |
|
Action
| Modify the process to use a supported scripting language. |
|
|
BEA-2031654
|
Error: The context node is of unsupported type 'actualType' when it is required to be of type 'expectedType'.
|
Description
| The context node for the expression is not of the expected type. This should never happen. |
|
Action
| Contact Technical Support. |
|
|
BEA-2031655
|
Error: Variable 'variable' is a message. It must be either a variable defined by a schema type or a schema variable or a message part.
|
Description
| The variable used in the expression is defined as a message type. Message type variables cannot be referenced directly - only their parts can be referenced. This should be caught by validation during deployment. |
|
Action
| Modify the expression to use the $(variable).(part) syntax. |
|
|
BEA-2031656
|
Error: Variable 'variable' is not a message but is being referenced as though it has a part 'part'.
|
Description
| The variable is being used via the $(variable).(part) but it is not a message type variable. This should be caught by validation during deployment. |
|
Action
| Modify the expression to use only $(variable) syntax. |
|
|
BEA-2031657
|
Error: Variable 'variable', defined as message type 'messageType', does not contain part 'part'.
|
Description
| The variable is defined by a message type that does not have the given part. This should be caught by validation during deployment. |
|
Action
| Modify the expression to use a part that the message type does have. |
|
|
BEA-2031658
|
Error: Link status for 'link' is being referenced before is has been set.
|
Description
| The link is being referenced before it has been set. This is generally a problem with the process definition but it could be a timing issue. |
|
Action
| Modify the process to ensure that the link is always set before it is referenced. |
|
|
BEA-2031659
|
Error: Variable 'variable' is being referenced before it has been initialized with a value.
|
Description
| The variable is being referenced before it has been initialized. This is generally a problem with the process definition but it could be a timing issue. |
|
Action
| Modify the process to ensure that the variable is always initialized before it is referenced. |
|
|
BEA-2031660
|
Error: Variable 'variable' is undefined.
|
Description
| The variable has not been declared before it is referenced. This should be caught by validation during deployment. |
|
Action
| Contact Technical Support. |
|
|
BEA-2031661
|
Error: The xml fragment for the literal has more than 1 root element.
|
Description
| An XML literal must have a single root element. This should be caught by validation during deployment. |
|
Action
| Contact Technical Support. |
|
