Glen,AxisFault takes an exception and puts that into the SOAPFaullt details section as a stack trace.
As this did not suit my needs, I wrote (well, hacked) a generic SOAPFaultExecption class that then use to render appropriate SOAPFaults based on sublcasses of that SOAPFaultException.
I attached the SOAPFaultException and an abstract subclass, WSRFBaseFaultException, that then is concretised by other (not attached) Exception.
Hope this is useful to you. Cheers, Michel
SOAPFaultException.java
Description: Binary data
WSRFBaseFaultException.java
Description: Binary data
On 13 Apr 2006, at 14:35, Glen Daniels wrote:
Hi Sanjiva:Do the various AxisFault constructors not fit the bill? For example: AxisFault(QName faultCode, String faultReason, Throwable cause)OK, so I can get an AxisFault. Is there an easy way to turn that into a SOAPEnvelope?(And there are other more flexible ones as well of course.)Hm... I just took a look at the AxisFault constructors, and they could use some cleanup - they're very confusing right now, IMHO. For instance, there are both "messageText" and "reason" arguments in various constructors... it should be clear how to take String message and put it in an AxisFault (which should become both the Exception message and the SOAP fault reason). Again, just an indication that some more polish is needed.--Glen
