Is it possible to throw a BPELFault from a custom xpath function?

Question

I'm probably revealing my lack of java chops here, but I'd like to know if there's a way to throw a BPELFault from the "call" method within a custom xpath function.
The interface for IXPathFunction seems to dictate that "call" throws only an XPathFunctionException and the bpel server doesn't handle this exception properly. It records the exception in the logs but then the process just dies.
Right now I have this (simplified code):
public Object call(IXPathContext context,
List args) throws XPathFunctionException
if (args.size() == 1)
// do some stuff and return a value
throw new XPathFunctionException( "hexToInt() requires one string argument." );
What I want to have is something like this:
public Object call(IXPathContext context,
List args) throws BPELFault
if (args.size() == 1)
// do some stuff and return a value
BPELFault fault = new BPELFault(
new javax.xml.namespace.QName("http://schemas.xmlsoap.org/ws/2003/03/business-process/",
"selectionFailure"));
fault.setPart("code", "intToHex");
fault.setPart("summary", "hexToInt() requires one string argument.");
throw fault;
If I do this, the compiler rejects it saying that "call" must throw XPathFunctionException. Is there a way to extend the IXPathFunction interface to allow it to throw a useful fault?
Thanks!
Sean

Answer 1

Yeah, I'm using that patch (otherwise the process just crashes and you don't have a chance to catch the fault, even in a catchAll). Within the catchAll you can get the details from the error with something like this:
<copy>
<from expression="concat(ora:getFaultName(),'')"/>
<to variable="processFault" part="payload" query="/ns4:summary"/>
</copy>
<copy>
<from expression="concat(ora:getFaultAsString(),'')"/>
<to variable="processFault" part="payload" query="/ns4:detail"/>
</copy>