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=19682>. 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=19682 non-AxisFault exceptions don't have details serialized ------- Additional Comments From [EMAIL PROTECTED] 2003-05-28 04:04 ------- OK, let me see if I understand this problem. We're already testing that we throw the correct fault on the client when given server faults are generated (see test.wsdl.faults) - but this is only the case when we're using faults generated by WSDL2Java, so they all inherit from AxisFault. As I see it, you have an Exception class on the server with some data fields; an Exception which is *not* derived from AxisFault (and therefore has no generated writeDetails() method).... and you want this Exception class to serialize itself correctly. Right? The question I have is on the client side - do you want to be able to *deserialize* to a non-AxisFault Exception over there too (that's tricky and we don't do it yet), or is it enough to just get the data correctly serialized so that faults that were built from the WSDL via WSDL2Java will be correctly thrown on the client side?
