SOA 11g - FabricInvocationException when calling EJB Service

Question

Hi All,
I have a case where a stateles ejb needs to be called from a composite. It is imported via EJB Service adapter.
The question here is: How to correctly receive a thrown exception as the fault type it is supposed to be?
Some more details of the problem:
The invocation of EJB works just fine. The called method executes, returns correct responses. Except for when throwing an exception.
I'm throwing a ProcessingException, which I would expect to receive as a fault. The message type is present in the automatically generated WSDL.
Instead I am getting:
<fault>
<bpelFault>
<faultType>0</faultType>
<remoteFault>
<part name="summary">
<summary>oracle.fabric.common.FabricInvocationException: Unable to invoke</summary>
</part>
<part name="detail">
<detail>Throwing requested exception</detail>
</part>
<part name="code">
<code>null</code>
</part>
</remoteFault>
</bpelFault>
</fault>
<faultType>
<message>0</message>
</faultType>
The detail part is actually the text I use to create the exception in EJB, this could be used as a workaround to identify the exception, but a fault of correct type would work better with fault handling and policies.
relevant part of the log:
EJBService.getNewMessageIds: [proc]
throwing business exception
<Dec 6, 2011 12:18:22 PM CET> <Error> <oracle.soa.bpel.engine.ws> <BEA-000000> <got FabricInvocationException
de.other.pack.ProcessingException: Throwing requested exception
     at com.oracle.os6.SessionEJBBean.getNewMessageIds(SessionEJBBean.java:38)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)

Answer 1

When using EJB3 with WTC, does my bean need to implement TuxedoService, TuxedoServiceHome or both?
Does my interface need to implement TuxedoService, TuxedoServiceHome or both?
I suspect this is what caused the ClassCastException in the previous post.
These interfaces are not documented anywhere.