<detail> contains information specific to the fault in question, and sometimes the package that created it. In this case, the stack trace is just a standard Java printStackTrace() output, and anyone who cares to look for the <stacktrace> element can get at it. We've discussed putting in a switch to turn this on and off for a service/engine, in fact.
So the short answer is no, it doesn't follow a particular standard. For things like this, and exception class names, it might be nice if all the Java implementations agreed on a standard, and that might be something you see in future revs of JAX-RPC. --Glen > -----Original Message----- > From: Thomas Börkel [mailto:tb@;ap-ag.com] > Sent: Thursday, October 17, 2002 10:48 AM > To: Axis Dev Mailinglist > Subject: SOAP stacktrace > > > HI! > > If the server throws an exception then Axis puts the > stacktrace into the <detail> tag of the response with > namespace "ns2". Does this follow some standard, so should > other SOAP implementations (like .NET) understand this? The > current implementation of .NET (using generated proxy > classes) does not even provide the text of the fault detail, > only the fault string. > > Thanks! > > Regards, > Thomas >
