custom soapfault resolver triggering but not finding SoapFault in SoapBody

[Stuart Rogers]

My Spring Web Service Client has this custom resolver to catch SoapFaults:

    public class MySoapFaultResolver extends SoapFaultMessageResolver implements FaultMessageResolver 
    {
        private static Logger logger = Logger.getLogger( MySoapFaultResolver.class);
        
        @Override
        public void resolveFault(WebServiceMessage wsm) throws IOException 
        {
            logger.debug("entering");
                    
    //      SOAPMessage soapMessage = (SOAPMessage) wsm;   cant cast to this
            SoapMessage soapMessage = (SoapMessage) wsm;
            
            if( soapMessage == null) {
                logger.debug("soapMessage is null");
            } else {
                logger.debug("soapMessage is not null");
                QName om_fc = soapMessage.getFaultCode();
                String om_frs = soapMessage.getFaultReason();
                logger.debug("om_fc:" + om_fc);
                logger.debug("om_frs:" + om_frs);
                if( soapMessage.getSoapBody() == null) {
                    logger.debug("soap body is null");               
                } else {
                    logger.debug("soap body is not null"); 
                    SoapBody sb = soapMessage.getSoapBody();
                    logger.debug( sb.toString() ); // prints org.springframework.ws.soap.saaj.SaajSoap11Body@1d23bf4
                    QName sb_name = sb.getName();
                    logger.debug("sb_name:" + sb_name);
                    Iterator<QName> iter_attr_sb = sb.getAllAttributes();
                    while( iter_attr_sb.hasNext()) {
                        QName qname = iter_attr_sb.next();
                        String qname_valu = sb.getAttributeValue(qname);
                        logger.debug("attribute: " + qname + ":" + qname_valu);
                    }
                    if( sb.hasFault()) {
                        logger.debug("soap body has fault");
                        SoapFault sff = sb.getFault();
                        QName fc = sff.getFaultCode();
                        String fsr = sff.getFaultStringOrReason();
                        logger.debug("fc:" + fc);
                        logger.debug("fsr:" + fsr);
                        Iterator<QName> iter_attr = sff.getAllAttributes();
                        while( iter_attr.hasNext()) {
                            QName qname = iter_attr.next();
                            String qname_valu = sff.getAttributeValue(qname);
                            logger.debug("attribute: " + qname + ":" + qname_valu);
                        }
                        if( sff.getFaultDetail() == null) {
                            logger.debug("fault has no details");
                        } else {
                            logger.debug("fault has details");
                            SoapFaultDetail faultDetail = sff.getFaultDetail();
                            Iterator<SoapFaultDetailElement> detailEntries = faultDetail.getDetailEntries();
                            while( detailEntries.hasNext()) {
                                SoapFaultDetailElement detailElement = detailEntries.next();
                                logger.debug("Found SoapFaultDetailElement name:" + detailElement.getName());
                            }
                        }
                    } else {
                        logger.debug("soap body does not have fault");    
                    }
                }
            }
            logger.debug("exiting");
            
            SoapFaultClientException sfce = new SoapFaultClientException( soapMessage);
            throw new IOException( "cursesfoiledagain", sfce);
        }

which gets executed when this fault comes back from the service:

    <soap:Envelope>
      <soap:Body>
        <soap:Fault>
          <faultcode>soap:Server</faultcode>
          <faultstring>Could not open connection; nested exception is org.hibernate.exception.GenericJDBCException: Could not open connection</faultstring>
        </soap:Fault>
      </soap:Body>
    </soap:Envelope>

and writes this to the logfile:

    MySoapFaultResolver-resolveFault] - entering
    MySoapFaultResolver-resolveFault] - soapMessage is not null
    MySoapFaultResolver-resolveFault] - om_fc:null
    MySoapFaultResolver-resolveFault] - om_frs:null
    MySoapFaultResolver-resolveFault] - soap body is not null
    MySoapFaultResolver-resolveFault] - org.springframework.ws.soap.saaj.SaajSoap11Body@1d23bf4
    MySoapFaultResolver-resolveFault] - sb_name:{http://schemas.xmlsoap.org/soap/envelope/}Body
    MySoapFaultResolver-resolveFault] - soap body does not have fault
    MySoapFaultResolver-resolveFault] - exiting

I am baffled by why the code isn't finding the SoapFault within the SoapBody. Can anyone shed some light on this?
It's almost as if the casting wipes out most of the underlying information, but googling around finds pleny of examples that use this idiom.

TIA,

Still-learning Steve