The OSB Transform catalog contains messages in the range
BEA382500 - BEA382599. Messages in this catalog are part of the
stages.transform.messages Internationalization package and the
stages.transform.messages Localization package.
|
BEA-382500
|
Error: OSB Service Callout action received SOAP Fault response
|
Description
| OSB Service Callout action has received a SOAP Fault response from the web service that was invoked. The contents of the received SOAP Fault can be seen in the details element of $fault message context variable. |
|
|
BEA-382501
|
Error: OSB Service Callout action received an unrecognized response
|
Description
| The service invoked by OSB Service Callout action has returned payload that was not consistent with the declared service binding type and as a result could not be properly parsed by OSB. For example, this can happen if a service that was registered with XML binding type, returned non well-formed XML payload. The contents of the received response can be seen in the details element of $fault message context variable. |
|
Action
| Check the contents of response payload in $fault variable to see why it is inconsistent with the declared service binding type |
|
|
BEA-382502
|
Error: OSB Service Callout action received an error response
|
Description
| The service invoked by OSB Service Callout action has indicated that an error condition other than a SOAP fault has occured. For example, this may happen when an HTTP 404 (Page Not Found) error code is received from an external HTTP service. The contents of the received response (if any) can be seen in the details element of $fault message context variable. |
|
Action
| Check the contents of response payload in $fault variable to see what the problem with service invocation is |
|
|
BEA-382505
|
Error: OSB Validate action failed validation
|
Description
| The input expression has failed validation according to provided schema resource. The details of the validation error, such as specific error message, location of the invalid XML, etc. can be seen in the details element of $fault message context variable |
|
Action
| Check the contents of $fault variable to see the source of the validation failure |
|
|
BEA-382510
|
Error: OSB Assign action failed updating variable "variable": msg
|
Description
| There was an error during the evaluation of XQuery/XSLT expression during the execution of Assign action. This could happen if an XQuery expression the result of which is being assigned to a variable, results in a runtime error from the XQuery evaluation engine. There should be a specific error message that will pinpoint the source of the problem. |
|
Action
| Check the configured XQuery expression for potential syntactic or semantic problems |
|
|
BEA-382511
|
Error: OSB Delete action failed updating variable "variable": msg
|
Description
| There was an error during the execution of Delete action. This could happen if the specified XPath expression is not a valid expression or results in a runtime error from XPath evaluation engine. There should be a specific error message that will pinpoint the source of the problem. |
|
Action
| Check the configured XPath expression for potential syntactic or semantic problems |
|
|
BEA-382512
|
Error: OSB Insert action failed updating variable "variable": msg
|
Description
| There was an error during the execution of Insert action. This could happen if an XQuery expression the result of which is being inserted into a variable, results in a runtime error from the XQuery evaluation engine. There should be a specific error message that will pinpoint the source of the problem. |
|
Action
| Check the configured XQuery expression for potential syntactic or semantic problems |
|
|
BEA-382513
|
Error: OSB Replace action failed updating variable "variable": msg
|
Description
| There was an error during the execution of Replace action. This could happen if an XQuery expression the result of which is being replaced in a variable, results in a runtime error from the XQuery evaluation engine. There should be a specific error message that will pinpoint the source of the problem. |
|
Action
| Check the configured XQuery expression for potential syntactic or semantic problems |
|
|
BEA-382514
|
Error: OSB Rename action failed updating variable "variable": msg
|
Description
| There was an error during the execution of Rename action. This could happen if the specified XPath expression is not a valid expression or results in a runtime error from XPath evaluation engine. There should be a specific error message that will pinpoint the source of the problem. |
|
Action
| Check the configured XPath expression for potential syntax or semantic problems |
|
|
BEA-382515
|
Error: Callout to java method "method" resulted in exception: msg
|
Description
| Java method specified in Java Callout action was invoked and resulted in an exception. The exception details should be part of the error message. |
|
|
BEA-382516
|
Error: Failed to evaluate expression for callout to java method "method". Argument index: argIndex, exception: errormsg
|
Description
| There was an error evaluating one or more arguments to a Java callout method. This could happen if an XQuery expression the result of which is being used as an argument to java method, results in a runtime error from the XQuery evaluation engine. There should be a specific error message that will pinpoint the source of the problem. |
|
Action
| Check the configured XQuery expression for potential syntactic or semantic problems |
|
|
BEA-382517
|
Error: Failed to assign the result of java callout to variable. Method: method, variable: varname, exception: errormsg
|
Description
| There was an error while assigning the result of invoked Java method to specified message context variable. This could happen if the variable being assigned to is a read-only system variable (e.g. $operation), or a system variable whose type does not match that returned by the invoked Java method. There should be a specific error message that will pinpoint the source of the problem. |
|
|
BEA-382518
|
Error: Security exception while calling to java method "method". Service account: sacct. t
|
Description
| There was an error while setting up the security context for java callout method. This could happen if there is a problem retrieving the credentials of specified service account. There should be a specific error message that will pinpoint the source of the problem. |
|
|
BEA-382519
|
Error: The XmlObject returned by a java callout must be a simple type, an attribute or an element.
|
Description
| Java method invoked returned an unsupported type of XML Bean. The only supported types are simple types, attributes or element. |
|
|
BEA-382520
|
Error: Unexpected error executing if-then-else expression
|
Description
| An unexpected runtime exception has occured during the execution of the if-then-else action. |
|
Action
| Contact technical support |
|
|
BEA-382521
|
Error: Variable targeted for rename is not XML or MFL
|
Description
| The variable that is targeted for rename operation does not hold XML data. |
|
Action
| Check the value of the variable that is targeted for rename operation. You can use Log action to see the value of any message context variable at runtime. |
|
|
BEA-382522
|
Error: Variable targeted for replace is not XML or MFL
|
Description
| The variable that is targeted for replace operation does not hold XML data. |
|
Action
| Check the value of the variable that is targeted for rename operation. You can use Log action to see the value of any message context variable at runtime. |
|
|
BEA-382523
|
Error: The outbound variable has not been initialized
|
Description
| This is an unexpected error that occured due to incorrect state of the pipeline at runtime |
|
Action
| Contact technical support |
|
|
BEA-382524
|
Error: Failed to perform validation
|
Description
| An unexpected runtime error has occured during the execution of validate action. There should be a specific error message that will pinpoint the source of the problem. |
|
Action
| Contact technical support |
|
|
BEA-382525
|
Error: Variable targeted for validate is not XML or MFL
|
Description
| The variable that is targeted for validate operation does not hold XML data. |
|
Action
| Check the value of the variable that is targeted for validate operation. You can use Log action to see the value of any message context variable at runtime. |
|
|
BEA-382526
|
Error: Variable targeted for insert is not XML or MFL
|
Description
| The variable that is targeted for insert operation does not hold XML data. |
|
Action
| Check the value of the variable that is targeted for insert operation. You can use Log action to see the value of any message context variable at runtime. |
|
|
BEA-382527
|
Error: Inserting the result of this expression will create an invalid (multi-rooted) document
|
Description
| Inserting the result of this expression will create an invalid (multi-rooted) document. One way this could happen is if ones tries to insert (some) element node before . in $body message context variable |
|
Action
| Check the value of the variable that is targeted for insert operation. You can use Log action to see the value of any message context variable at runtime. |
|
|
BEA-382528
|
Error: Failed to insert after
|
Description
| Inserting the result of this expression after specified XPath resulted in an error. |
|
Action
| Check the value of the variable that is targeted for insert operation. You can use Log action to see the value of any message context variable at runtime. |
|
|
BEA-382529
|
Error: Cannot insert as a child of an attribute
|
Description
| It is illegal to insert as a child of an attribute |
|
Action
| Check the value of the variable that is targeted for insert operation. You can use Log action to see the value of any message context variable at runtime. |
|
|
BEA-382530
|
Error: Unable to insert after first child
|
Description
| Unable to insert after first child as there was no child elements of specified XPath expression |
|
Action
| Check the value of the variable that is targeted for insert operation. You can use Log action to see the value of any message context variable at runtime. |
|
|
BEA-382531
|
Error: Unable to insert after last child
|
Description
| Unable to insert after child element |
|
Action
| Check the value of the variable that is targeted for insert operation. You can use Log action to see the value of any message context variable at runtime. |
|
|
BEA-382532
|
Error: Only attributes may be inserted next to another attribute
|
Description
| Only attributes may be inserted next to another attribute |
|
Action
| Check the value of the variable that is targeted for insert operation. You can use Log action to see the value of any message context variable at runtime. |
|
|
BEA-382533
|
Error: Only elements and simple values may be inserted next to or inside of another element
|
Description
| Only elements and simple values may be inserted next to or inside of another element |
|
Action
| Check the value of the variable that is targeted for insert operation. You can use Log action to see the value of any message context variable at runtime. |
|
|
BEA-382534
|
Error: Content targeted for replace is not an element or an attribute
|
Description
| Content targeted for replace is not an element or an attribute |
|
Action
| Check the value of the variable that is targeted for replace operation. You can use Log action to see the value of any message context variable at runtime. |
|
|
BEA-382535
|
Error: An attribute may only be replaced with an attribute
|
Description
| An attribute may only be replaced with an attribute |
|
Action
| Check the value of the variable that is targeted for replace operation. You can use Log action to see the value of any message context variable at runtime. |
|
|
BEA-382536
|
Error: An element or its contents may only be replaced with elements and simple values
|
Description
| An element or its contents may only be replaced with elements and simple values |
|
Action
| Check the value of the variable that is targeted for replace operation. You can use Log action to see the value of any message context variable at runtime. |
|
|
BEA-382537
|
Error: Invalid SOAP RPC document - part "name" is not defined in the WSDL definitions.
|
Description
| The response to service callout contained invalid data according to WSDL defintion of the service being invoked. |
|
Action
| Check the response payload of service invocation and make sure it conforms to the WSDL definitions for the service. The contents of the received response can be seen in the details element of $fault message context variable. |
|
|
BEA-382538
|
Error: Invalid SOAP RPC document - part name occurs more than once.
|
Description
| The response to service callout contained invalid data according to WSDL defintion of the service being invoked. |
|
Action
| Check the response payload of service invocation and make sure it conforms to the WSDL definitions for the service. The contents of the received response can be seen in the details element of $fault message context variable. |
|
|
BEA-382539
|
Error: Invalid SOAP RPC document - part name contains more than one XML element
|
Description
| The response to service callout contained invalid data according to WSDL defintion of the service being invoked. |
|
Action
| Check the response payload of service invocation and make sure it conforms to the WSDL definitions for the service. The contents of the received response can be seen in the details element of $fault message context variable. |
|
|
BEA-382540
|
Error: Unexpected error - invalid internal state occured during the execution of service callout action
|
Description
| An unexpected error had occured during the execution of service callout action |
|
Action
| Contact technical support |
|
|
BEA-382541
|
Error: Invalid SOAP RPC document - part "name" is required but not present.
|
Description
| The response to service callout contained invalid data according to WSDL defintion of the service being invoked. |
|
Action
| Check the response payload of service invocation and make sure it conforms to the WSDL definitions for the service. The contents of the received response can be seen in the details element of $fault message context variable. |
|
|
BEA-382542
|
Error: The Transport Mode is set to "request-only". A Service Callout only supports "request-response" communications.
|
Description
| The Transport Mode is set to "request-only". Service Callout action only supports "request-response" communications. |
|
Action
| Check the contents of $outbound message context variable to make sure the tranport mode element is set properly. One can use Log action to see the contents of any message context variable at runtime |
|
|
BEA-382543
|
Error: Invalid message: the SOAP Header value is not an XML instance
|
Description
| The value of the message context variable used to set SOAP headers for service callout action does not contain valid XML |
|
Action
| Check the contents of specified message context variable to make sure it is set properly. One can use Log action to see the contents of any message context variable at runtime |
|
|
BEA-382544
|
Error: Invalid message: the message is not an XML instance
|
Description
| The value of the message context variable used to set SOAP body for service callout action does not contain valid XML |
|
Action
| Check the contents of specified message context variable to make sure it is set properly. One can use Log action to see the contents of any message context variable at runtime |
|
|
BEA-382545
|
Error: Unexpected error - the part schema type cannot be found
|
Description
| An unexpected error had occured during the execution of service callout action during the parsing phase of the service callout response |
|
Action
| Contact technical support |
|
|
BEA-382546
|
Error: Unexpected error - mismatch between configuration and WSDL definition
|
Description
| An unexpected error had occured during the execution of service callout action during the parsing phase of the service callout response |
|
Action
| Contact technical support |
|
|
BEA-382547
|
Error: The value for part "name" is not valid. An XML Element is expected.
|
Description
| An error had occured during the execution of service callout action during the phase when an outbound request payload gets constructed due to the fact that the configured message context variable does not contain valid XML element. |
|
Action
| Check the contents of specified message context variable to make sure it is set properly. One can use Log action to see the contents of any message context variable at runtime |
|
|
BEA-382548
|
Error: Unable to find the type definition of the part name
|
Description
| An error had occured during the execution of service callout action during the phase when an outbound request payload gets constructed due to missing or invalid type information in WSDL definitions |
|
Action
| Check the registered WSDL definition for proper semantic type infomation for the part in question |
|
|
BEA-382549
|
Error: Error accessing information from the target WSDL service
|
Description
| An error had occured during the execution of service callout action during the phase when an outbound request payload gets constructed due to not being able to access service WSDL definition. There should be a specific message that will point to the cause of the error. |
|
Action
| Check that the corresponding WSDL definition is properly registered |
|
|
BEA-382550
|
Error: Setting quality of service to Exactly Once in service callout action is not supported for service name
|
Description
| Setting quality of service to Exactly Once in service callout action is not supported for selected service. Quality of service can be set to Exactly Once only if the service transport endpoint is Transactional and the message pattern is one-way or synchronous. |
|
Action
| Check the pipeline configuration to make sure that the quality of service is not set to Exactly Once via Routing Options or some other action that changes the contents of $outbound message context variable. You can use Log action to see the value of any message context variable at runtime. |
|
|
BEA-382551
|
Error: XQuery expression did not return the non-empty source to apply the mfl transformation.
|
Description
| XQuery expression did not return the non-empty source to apply the mfl transformation. |
|
Action
| Check the XQuery expression to make sure that it returns a non-empty input to apply the mfl transformation. You can use Log action to see the value of XQuery expression at runtime. |
|
|
BEA-382552
|
Error: Binary content reference ref is not valid.
|
Description
| Binary content reference is not valid. It should be inserted by the pipeline as a result of passing binary content to the pipeline. |
|
Action
| Check the binary-content ref attribute on which the mfl transformation is applied. binary-content element should be inserted as a result of passing binary content to the pipeline. You can use Log action to see the value of this ref attribute at runtime. |
|
|
BEA-382553
|
Error: Input to non-xml to xml mfl transformation is invalid.
|
Description
| Input to the transformation should be non-empty text or the binary data represented by binary-content element in the pipeline. XML input is not allowed. |
|
Action
| Make sure that input expression returns the text or the binary-content ref attribute inserted by the pipeline as a result of passing binary content to the OSB. You can use Log action to see the value of this expression at runtime. |
|
|
BEA-382554
|
Error: XQuery expression evaluates to an invalid MFL resource name name.
|
Description
| XQuery expression did not return the valid MFL resource name. It should evaluate to an existing mfl resource in the OSB at runtime. |
|
Action
| Make sure that XQuery expression should evaluate to a existing mfl resource in the OSB at runtime. You can use Log action to see the value of this expression at runtime. |
|
|
BEA-382555
|
Error: XML to Binary mfl transformation failed for the MFL Resource name : errorMsg
|
Description
| XML to Binary mfl transformation failed. There should be a specific error message that will pinpoint the source of the problem. |
|
Action
| Check the configured mfl resource and the input data for potential syntactic or semantic problems. |
|
|
BEA-382556
|
Error: Binary to XML mfl transformation failed for the MFL Resource name : errorMsg
|
Description
| Binary to XML mfl transformation failed. There should be a specific error message that will pinpoint the source of the problem. |
|
Action
| Check the configured mfl resource and the input data for potential syntactic or semantic problems. |
|
|
BEA-382557
|
Error: No source was found in source repository with ref 'ref'.
|
Description
| No source was found in source repository with ref 'ref', which was the result of configured XQuery expression |
|
Action
| Check the XQuery expression to make sure that it returns proper result. You can use Log action to see the value of an XQuery expression at runtime. |
|