> not quite easy, many fields are private fields. > Why now add a function in the AxisFault to add some elements ?
Yes you can modify your AxisFault or extend it. But the result should be the same. Your information is serialized only if its in the fields of AxisFault (ex. detail). > Yes, but by having you own exception class, you may distinct buisness > exception ( exception launch by your own code ) and technical > exception ( launch for other reason ). This is true. But you can also do this by specifying the faultcode. > I am sure that better solution can be found, but how to keep the > interoperability with the other lg ? what the spec says about > fault message ? The normal behaviour would be to use the classes generated by WSDL2Java. These are correct. This way you conform to the WSDL used. It only remains to serialize somehow this exception class. This shouldn't be much of a problem because your excpetion class is basically a bean. However Axis guys had some trouble doing this. I don't know the details. Lack of time I guess. > This is not easy because, we have to access private field of the class > Exception ( which is mostly implemeted in native code ) I'm building an xml tree with my specific exception information and set in the detail field of an AxisFault (setDetailString or setDetailElement or something like that). This works for me, but this is not too nice. I have to build the xml myself. :(
