Handling Faults in asynchronous process SOA11G

Question

I could implement RuntimeFault.wsdl in synchronous process, but I cannot to do the smae in asynchronous process.
What is the difference in implementing it.
I want to handle wsdl (partner link) fault in during invoke activity. But when I add this
<wsdl:fault name="ImportOrderStatusFault" message="ns1:RuntimeFaultMessage"/>
in my bpel process wsdl I get error, wsdl not expected.
Also, when I use bpel:remoteFault, bpel:bindingFault or catchAll ,and use reply activity to client, I get error in reply activity.
Also, in asynchronous process, i cannot use throw activity. Now, if source system invokes my bpel asynchronous process, and there is WSDL Fault in Partner Link. Would source know that there is an exception ?
Thanks

Answer 1

in your async process you have something like
    <portType name="getEmployee">
        <operation name="initiate">
            <input message="client:EmployeeRequestMessage"/>
        </operation>
    </portType>
    <portType name="getEmployeeCallback">
        <operation name="onResult">
            <input message="client:EmployeeResponseMessage"/>
        </operation>
       <operation name="onError">
         <input message="client:yourErrorMessage"/>
       </operation>
    </portType>in your bpel you catch the error and in the catch handler you do the invoke back just like you do the callback in your normal flow, only this time you call onError instead of onResult
Or if you don't want the use a seperate callback (onError) you could still use the onResult in the catch handler, but before the invoke you need to construct the message you want to reply and assign that to lets say the outputVariable (if this is the one used by the callback in the error catch handler)