Perhaps, i'm too picky, but I'd like to be able to control the prefix names
of exceptions that are thrown in my service. I know... REALLY picky! Let me
show you my current output after I throw soapfault:

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";>
   <soap:Body>
      <soap:Fault>
         <faultcode>soap:client</faultcode>
         <faultstring>blah blah blah try again</faultstring>
         <detail>
            <ns1:MyExceptionClass xmlns:ns1="http://my.custom.namespace"/>
         </detail>
      </soap:Fault>
   </soap:Body>
</soap:Envelope>


I'd like for this to appear maybe like:

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";>
   <soap:Body>
      <soap:Fault>
         <faultcode>soap:client</faultcode>
         <faultstring>blah blah blah try again</faultstring>
         <detail>
            <custom:MyExceptionClass
xmlns:custom="http://my.custom.namespace"/>
         </detail>
      </soap:Fault>
   </soap:Body>
</soap:Envelope>


this is the code to generate the above fault:

                return postDatedAdapter.getEligibility(request, credentials);
                } catch (MyExceptionClass e){
                        throw new SoapFault(e.getMessage(), e, new
QName("http://schemas.xmlsoap.org/soap/envelope/";, "client"));
                }

I have a namespace mapper in my spring configuration, which works during
normal operation, but not on the exceptions:

        <util:map id="nameSpaceMap">
            <entry key="http://my.custom.namespace"; value="custom" />
        </util:map>



Not a panic situation if it can't be done... Just nit picking. Thanks!
-- 
View this message in context: 
http://www.nabble.com/Controlling-namespace-prefixes-in-SoapFaults-tp25153601p25153601.html
Sent from the cxf-user mailing list archive at Nabble.com.

Reply via email to