On 10/4/07, Jens Goldhammer <[EMAIL PROTECTED]> wrote: > > Ok, I have done this. And I found an interesting thing: If I put a correct > instance-id into the request for the method resume, the service works > correctly. If I put an incorrect value into the request, I get following > response: > > <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/ > "> > <soapenv:Body> > <soapenv:Fault xmlns:java="java:package java.lang.reflect, Java > Platform API Specification, version 1.5"> > > <faultcode>java:java.lang.reflect.InvocationTargetException</faultcode> > <faultstring>Invocation of method resume in management interface > failed!</faultstring> > <detail> > <Exception>org.apache.ode.axis2.OdeFault: Invocation of method > resume in management interface failed! > Caused by: org.apache.ode.bpel.pmapi.InvalidRequestException: The process > "null" is available. > </Exception> > </detail> > </soapenv:Fault> > </soapenv:Body> > </soapenv:Envelope> > > I think, this is business fault and should return a defined fault. Maybe > you > can add wsdl faults for all methods.
I agree we should map this exception to a WSDL Fault. I created a new issue for this http://issues.apache.org/jira/browse/ODE-193 alex
