Affects Version/s: 1.5.1
Fix Version/s: None
java version "1.6.0_16"
Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
Java HotSpot(TM) Client VM (build 14.2-b01, mixed mode, sharing)
* Eclipse Dynamic Web Project
* Apache Axis2 v1.5.1
We're creating a SOAP message, with a SOAPFault, and attempting to attach details.
Previous to Axis2 v1.5.1 (don't remember which version), we were doing:
detail = soapFaultObject.addDetail()
... and so on ...
After upgrading to v1.5.1, this now fails – no matter what you do, you will always get an EMPTY detail entry in your message.
The resulting XML has:
After much investigating, the problem appears to be that there is now a pre-created 'detail' object already on the SOAPFault, and if you call 'addDetail' again a SECOND detail is created. This detail object is completely ignored during serialization (not sure if it should be or not?).
The solution to this is then to do something like:
detail = soapFaultObject.getDetail()
if(detail == null)
Once this workaround is know, this is fairly minor impact – but without knowing the workaround, it has a fairly major effect!
I think that either:
a. The addDetail should actually add another detail, and this should actually get serialized properly.
b. The addDetail method should throw an exception if there is already a detail present.
c. There should not event BE an addDetail method.