Unable to find Fault variable in RemoteFault

If you are placing a catch block in your service invocation and trying to catch a system remotefault/bindingfault  , you can have following issues :

1. First , your faultVariable is not having any child element like code,summary and detail which are part of the RuntimeFault. 

2.  Second, when you try to compile the composite, you get below error:
Error(76): WSDL messageType "{http://schemas.oracle.com/bpel/extension}bindingFault" of variable "" is not defined in any of the WSDL files 

Reason for above issues and solution:
The reason why you get this is because when you select the system->RuntimeFault as type of fault in your fault handler, JDeveloper copies a wsdl named RuntimeFault.wsdl  from your <JDEVELOPER_HOME%\\integration\seed\soa\shared\bpel directory to your project and this wsdl contains following msg :

<?xml version="1.0" encoding="UTF-8"?>
<definitions name="RuntimeFault"
             targetNamespace="http://schemas.oracle.com/bpel/extension"
             xmlns:xsd="http://www.w3.org/2001/XMLSchema"
             xmlns="http://schemas.xmlsoap.org/wsdl/">

    <message name="RuntimeFaultMessage">
        <part name="code" type="xsd:string"/>
        <part name="summary" type="xsd:string"/>
        <part name="detail" type="xsd:string"/>
    </message>
</definitions>

And secondly, JDeveloper create the faultVariable in your BPEL file (.bepl) like this :

<variable messageType="bpelx:bindingFault" name="FaultVar"/>

Now if you observe, the RuntimeFault.wsdl is having the message name as "RuntimeFaultMessage" where as
the variable's messageType is messageType="bpelx:bindingFault" and it is this mismatch which is causing the above mentioned two issues .

To get rid of it, simply change the variables msg type from "bpelx:bindingFault" to "bpelx:RuntimeFaultMessage"  and you are good to go with your composite :
 <variable messageType="bpelx:RuntimeFaultMessage" name="FaultVar"/>

Comments

Post a Comment

Popular posts from this blog

Difference between Route, Service Callout, Publish

When you are first starting with OSB it can be a little tricky to determine when to use a Route, Service Callout or a Publish node.  All three can be used to call either a Business service or a local Proxy service.  You can use the following lists to determine which will best fit your needs. Route Last node in request processing.  It can be thought of as a bridge between request pipeline processing and the response pipeline processing. You can only execute one route in your Proxy Service. Can only be created in a route node. OSB will wait for the Route call to finish before continuing to process. If you are calling a Business service  and  you specify  Best Effort  for QoS (Quality of Service), then OSB will release the thread it is holding while the business service executes. If you are calling a Business service  and  you specify  Exactly Once  or  At Least Once  for QoS, then OSB will hold onto the thread while the business service executes. If you are calling a l
Read more

OSB actions in proxy service

Image
In this post we will see about different types of actions to message flows using the Oracle Service Bus Administration Console, such as route, publish, service callout, transport headers, conditional actions, error actions, and message transformation actions. Actions are the elements of pipeline stages, error handler stages, route nodes, and branch nodes that define how messages are to be defined as they flow through a pipeline            Action                           Description                     Dynamic Publish Publish a message to a service identified by an XQuery expression                          Publish Publish a message to a statically specified service.                        Publish Table Publish a message to zero or more statically specified services. Switch-style condition logic is used to determine at run time which services will be used for the publis
Read more

XQuery functions that supported by OSB

NAMESPACES ------------------------------------------------------------------------ xml=http://www.w3.org/XML/1998/namespace fn=http://www.w3.org/2004/07/xpath-functions op=http://www.w3.org/2004/07/xpath-operators err=http://www.w3.org/2004/07/xqt-errors fn-bea=http://www.bea.com/xquery/xquery-functions op-bea=http://www.bea.com/xquery/xquery-operators dt-bea=http://www.bea.com/xquery/xquery-datatypes var-bea=http://www.bea.com/xquery/xquery-variables xf-aug02=http://www.w3.org/2002/08/xquery-function op-aug02=http://www.w3.org/2002/08/xquery-operators xs=http://www.w3.org/2001/XMLSchema xsd=http://www.w3.org/2001/XMLSchema xdt=http://www.w3.org/2004/07/xpath-datatypes local=http://www.w3.org/2004/07/xquery-local-functions declare default function namespace "http://www.w3.org/2004/07/xpath-functions XQUERY FUNCTIONS ------------------------------------------------------------------------ fn:node-name($arg as node()?) as xs:QName? fn:
Read more