The ALSB Kernel catalog contains messages in the range
BEA395100 - BEA395999. Messages in this catalog are part of the
com.bea.wli.sb.messages Internationalization package and the
com.bea.wli.sb.messages Localization package.
|
BEA-395100
|
Error: The TokenIterator does not correspond to a XmlObject value
|
Description
| One of the pipeline actions has attempted to treat the result of XQuery expression as XML, whereas the actual return value was not XML |
|
Action
| Please check the pipeline configuration to make sure that the context in which the XQuery expression is used is consistent with the actual return value |
|
|
BEA-395101
|
Error: prolog declarations are not allowed for xquery snippets
|
Description
| The inline XQuery expression has prolog declarations, such as ''declare namespace'' statements. This is not allowed in inline XQuery expressions |
|
Action
| Please check the text of inline expression for prolog declarations. If those are really necessary, then register a XQuery resource and use it instead of an inline expression in your action. |
|
|
BEA-395102
|
Error: The given value is not of a supported type: className
|
Description
| One of the pipeline actions has passed an expression to XQuery evaluation engine that is not of recognized type |
|
Action
| Please check the configuration of the action to make sure the text of the expression is properly configured and has semantic meaning. Contact technical support. |
|
|
BEA-395103
|
Error: Unsupported XQuery Type: tokenType
|
Description
| While evaluating the result of XQuery expression, an unexpected XML token has been found. |
|
Action
| Please check the configuration of the action to make sure the text of the expression is properly configured and has semantic meaning. Contact technical support. |
|
|
BEA-395104
|
Error: The TokenIterator does not correspond to a single String value
|
Description
| The result of XQuery expression was expected to be a single String value and was something else. |
|
Action
| Please check the configuration of the action to make sure the text of the expression is properly configured and will result in a single String value |
|
|
BEA-395105
|
Error: The TokenIterator does not correspond to a single XmlObject value
|
Description
| The result of XQuery expression was expected to be a single XML object value and was something else. |
|
Action
| Please check the configuration of the action to make sure the text of the expression is properly configured and will result in a single XML object value |
|
|
BEA-395106
|
Error: Unexpected Error: the TokenSource does not contain an BEGIN ATTRIBUTE
|
Description
| There was an unexpected error while parsing the result of XQuery expression. A BEGIN ATTRIBUTE token was expected but not found |
|
Action
| Contact technical support |
|
|
BEA-395107
|
Error: Unexpected Error: the TokenSource does not contain an END ATTRIBUTE
|
Description
| There was an unexpected error while parsing the result of XQuery expression. A END ATTRIBUTE token was expected but not found |
|
Action
| Contact technical support |
|
|
BEA-395108
|
Error: Error parsing XML: msg
|
Description
| There was an unexpected error while parsing the result of XQuery expression. There should be a message that points to the cause of the problem |
|
Action
| Contact technical support |
|
|
BEA-395109
|
Error: Invalid number of arguments
|
Description
| The number of arguments to custom XQuery function did not match that which was expected |
|
Action
| Please check the pipeline action configuration that uses the custom XQuery function to make sure it is configured properly |
|
|
BEA-395110
|
Error: An unexpected error occurred, the runtime executor is in an illegal state.
|
Description
| An unexpected error has occured during the execution of XQuery or XSLT resource |
|
Action
| Contact technical support |
|
|
BEA-395111
|
Error: The XQuery expression used to specify the name of the XQuery resource did not result in a string value
|
Description
| The result of the XQuery expression is expected to be a single string value which is the full path to XQuery resource to execute |
|
Action
| Please check the XQuery expression to make sure it produces expected results. You can use Log action to see the value of this expression at runtime. |
|
|
BEA-395112
|
Error: XQuery expression evaluates to an invalid XQuery resource name resource.
|
Description
| XQuery expression did not return the valid XQuery resource name. It should evaluate to an existing XQuery resource at runtime. |
|
Action
| Make sure that XQuery expression should evaluate to a existing XQuery resource in ALSB at runtime. You can use Log action to see the value of this expression at runtime. |
|
|
BEA-395113
|
Error: The number of parameters for registered XQuery resource ref does not match that given to it at runtime
|
Description
| The number of input parameters given to XQuery resource at runtime does not match the number that he resource requires |
|
Action
| Double-check that the number of input arguments supplied in dynamic XQuery configuration matches that of the XQuery resource to be used at runtime |
|
|
BEA-395114
|
Error: XQuery resource ref expected an XQuery expression for XQuery parameter name but none was found
|
Description
| Each parameter to an XQuery resource needs to have an XQuery expression configured to be bound as its value at runtime. One or more of the parameters to the given XQuery is missing an expression for its value |
|
Action
| Double-check that all of the parameters to the XQuery resource have been properly supplied in dynamic XQuery configuration |
|
|
BEA-395115
|
Error: The value of input argument argName cannot be null or an empty string
|
Description
| The input argument value to the XQuery function is argValue; the argument value should not be null or empty string |
|
Action
| Please check the input argument argName value to make sure it does not result in a null or empty string.. |
|
