At some risk of redundancy:
Step 1: set up Aegis+JAX-WS environment with some exceptions on the
service interface (and of course implementation).
Step 2: observe that WSDL seems plausible.
Step 3: run unit test. The throw is
org.apache.cxf.binding.soap.SoapFault, not any of mine.
Step 4: In a state of distraction, leap to the stupid conclusion that
the use of @WebFault could somehow result in better behavior.
Step 5: Discover error of ways.
Step 6: Read source code and fail to locate any sign of a capability to
map a fault to a custom exception class on client -- which might only
prove that I can't read.
Step 7: send this message amongst others.