Binding Faults

Question

Hello, I need you to expand on an aspect of the BankTransferFlow demo. Specifically, the way faults are handled. When an exception is raised, the process catches the fact that a user defined exception has occurred, then copies a literal into a fault variable. How can this be exanded so that the variables within the exception can be inspected and copied by the process?
For example, the message in the wsdl is defined as follows, with NotEnoughBalanceExceptionType being defined as an xs:any type.
<message name="NotEnoughBalanceFaultMessage">
<part name="payload" type="tns:NotEnoughBalanceExceptionType"/>
</message>
So, when the error is thrown, within the ejb code,
if( curBalance < amount) throw new NotEnoughBalanceException(accountId, curBalance, amount);
An instance of NotEnoughBalanceException is created,
public class NotEnoughBalanceException extends Exception {
     private String accountId;
     private double balance;
     private double amount;
     NotEnoughBalanceException(String accountId, double balance, double amount)
          this.setAccountId( accountId );
          this.setAmount( amount );
          this.setBalance( balance );
How do I model the wsdl and bpel code to access the 3 variables from within the BPEL flow at runtime?
Thanks.

Answer 1

Hello guys,
did you manage to get a patch for your issue?
We have the same one here, a FabricInvocationException at the BPEL layer,
and in the logs
java.lang.ClassCastException: [B cannot be cast to com.bea.wli.sb.transports.client.SOAMessage
     at com.bea.wli.sb.transports.direct.OSBDirectConnection.invoke(Unknown Source)
     at com.bea.wli.sb.transports.direct.OSBDirectConnection.request(Unknown Source)
[ I use SOA Suite 11.1.1.5 ]
thanx
ydes