The OSB Kernel catalog contains messages in the range
BEA395130 - 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-395130
|
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-395131
|
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-395132
|
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-395133
|
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 OSB at runtime. You can use Log action to see the value of this expression at runtime. |
|
|
BEA-395134
|
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-395135
|
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-395136
|
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.. |
|
|
BEA-395137
|
Error: CustomXPathFunctionManager: Error during initialization! File: fileName. Error: t
|
Description
| There was an error parsing the contents of file fileName containing custom XPath function definitions |
|
Action
| Please check the contents of the file and make sure it conforms to specified XML schema and all restrictions on supported Java methods/types, etc. are followed |
|
|
BEA-395138
|
Warning: CustomXPathFunctionManager: Failed to register custom XPath function 'funcName'. Error: t
|
Description
| There was an error parsing the contents of file containing custom XPath function definitions |
|
Action
| Please check the contents of the file and make sure it conforms to specified XML schema and all restrictions on supported Java methods/types, etc. are followed |
|
|
BEA-395139
|
Error: No custom function with QName 'funcName' exists
|
Description
| An unexpected error has occured during the execution of XQuery resource |
|
Action
| Contact technical support |
|
|
BEA-395140
|
Error: Custom function name needs to be a non-empty string
|
Description
| The name of the custom XPath function needs to be a non-empty string |
|
Action
| Check the custom XPath function configuration file in ALSB_HOME\config\xpath-functions directory and make sure all entries conform to specified rule |
|
|
BEA-395141
|
Error: Custom function namespace needs to be a non-empty string
|
Description
| The namespace of the custom XPath function needs to be a non-empty string |
|
Action
| Check the custom XPath function configuration file in ALSB_HOME\config\xpath-functions directory and make sure all entries conform to specified rule |
|
|
BEA-395142
|
Error: Custom function class name needs to be a non-empty string
|
Description
| The name of the Java class for the custom XPath function needs to be a non-empty string |
|
Action
| Check the custom XPath function configuration file in ALSB_HOME\config\xpath-functions directory and make sure all entries conform to specified rule |
|
|
BEA-395143
|
Error: Custom function class method signature needs to be a non-empty string
|
Description
| The name of the Java class method for the custom XPath function needs to be a non-empty string |
|
Action
| Check the custom XPath function configuration file in ALSB_HOME\config\xpath-functions directory and make sure all entries conform to specified rule |
|
|
BEA-395144
|
Error: Custom function class className needs to be public
|
Description
| The Java class for the custom XPath function needs to have public scope |
|
Action
| Check the custom XPath function configuration file in ALSB_HOME\config\xpath-functions directory and make sure all entries conform to specified rule |
|
|
BEA-395145
|
Error: Custom Function class className has no methods
|
Description
| The Java class for the custom XPath function has no methods |
|
Action
| Check the custom XPath function configuration file in ALSB_HOME\config\xpath-functions directory and make sure all entries conform to specified rule |
|
|
BEA-395146
|
Error: No method with signature 'methodSig' was found in class className
|
Description
| The Java class for the custom XPath function has no method with the specified signature |
|
Action
| Check the custom XPath function configuration file in ALSB_HOME\config\xpath-functions directory and make sure all entries conform to specified rule |
|
|
BEA-395147
|
Error: Method 'methodSig' needs to be public static
|
Description
| The Java method for the custom XPath function has to be declared as public static |
|
Action
| Check the custom XPath function configuration file in ALSB_HOME\config\xpath-functions directory and make sure all entries conform to specified rule |
|
|
BEA-395148
|
Error: Unsupported Java class className used by custom XPath function
|
Description
| One or more of the input arguments and/or return values from a custom XPath function has a Java type not currently supported by this feature |
|
Action
| Check the custom XPath function configuration file in ALSB_HOME\config\xpath-functions directory and make sure all entries conform to specified rule |
|
|
BEA-395149
|
Error: Expected expected arguments. Got: found
|
Description
| The number of input arguments passed into custom XQuery function at runtime does not match the number of expected arguments specified by its corresponding Java method signature |
|
Action
| Check the custom XPath function configuration file in ALSB_HOME\config\xpath-functions directory and make sure all entries conform to specified rule |
|
|
BEA-395150
|
Error: Error invoking custom xquery java function: t
|
Description
| An runtime error has occured during the invocation of a custom XQuery function |
|
Action
| Check the server log and the corresponding exception stack trace to see additional information that might point to the cause of the error |
|
|
BEA-395151
|
Error: CustomXPathFunctionManager: Error during initialization! File: fileName Error: t
|
Description
| There was an error during initialization reading the contents of one or more Jar files in ALSB_HOME config xpath-functions directory |
|
Action
| Please check the contents of the directory |
|
|
BEA-395152
|
Warning: CustomXPathFunctionManager: arg does not exist or is not a directory. Skipping initialization entirely...
|
Description
| There was an error during initialization of custom xpath functions feature. The OSB configuration directory for xpath functions was not found |
|
Action
| Please check the contents of the directory |
|
|
BEA-395153
|
Error: CustomXPathFunctionManager: Custom function name 'arg' is not valid
|
Description
| Custom function name needs to be a valid NCName. See http://www.w3.org/TR/REC-xml-names/#NT-NCName for more information |
|
Action
| Check the custom XPath function configuration file in ALSB_HOME\config\xpath-functions directory and make sure all entries conform to specified rule |
|
|
BEA-395154
|
Warning: CustomXPathFunctionManager: Function with QName 'qname' and signature 'sig' cannot be registered as there is another function with the same QName
|
Description
| Custom function QNames needs to be unique |
|
Action
| Check the custom XPath function configuration file in ALSB_HOME\config\xpath-functions directory and make sure all entries conform to specified rule |
|
|
BEA-395155
|
Error: CustomXPathFunctionManager: Error during initialization! File: fileName Error(s): message
|
Description
| There was an error during initialization reading the contents of specified XML configuration file |
|
Action
| Check the custom XPath function configuration file(s) in ALSB_HOME\config\xpath-functions directory and make sure all entries conform to specified XML schema |
|
|
BEA-395156
|
Debug: Expression execution optimized for retrieval of inbound transport header 'arg' will be used instead of XQuery result evaluation
|