DO NOT REPLY [Bug 24275] New: - AxisFault should use Exception class name as fault code.

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24275>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24275

AxisFault should use Exception class name as fault code.

           Summary: AxisFault should use Exception class name as fault code.
           Product: Axis
           Version: 1.1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Basic Architecture
        AssignedTo: axis-dev@ws.apache.org
        ReportedBy: lycono@mindless.com


When AxisFault.makeFault is called with an exception that is NOT derived from
AxisFault, the resulting AxisFault has the fault code "Server.userException". 
It would seem more intuitive and useful to set the fault code to the full class
name of the Exception that is passed to makeFault.

For example, if I have a service hosted by Axis with an operation that throws
org.foo.MyException, the client will receive a fault with the fault code set to
Server.userException.  Since the fault code is a "unique" identifier for the
fault, it makes more sense to me that the client would see the fault code as the
full class name: org.foo.MyException.

Setting the fault code to Server.userException seems to defeat the purpose of
the fault code.