Are you able to solve this problem? I am also facing the same issue.
Our service is also a mediation service and faultcode, faultstring & faultactor in soap fault need to hold custom values returned by backend app, instead of having IS generated faultcode, faultstring & faultactor.
webMethods IS 7.1.2 has serious problem of generating wrapper arrays, instead of conforming to the actual document types. (link)
So we decided to go with WSDL first approach. The WSDL has request, response and fault structures defined. Imported the WSDL as provider and IS created its wrapper services and doc types respectively.
For success scenarios, I can see the output being returned appropriately in SOAP UI. But I am not able to receive the custom soap fault message at all.
The web service developer’s guide says
I tried to play with the underlying IS service and populate different fault documentTypes (generated by IS while importing WSDL), but of no use. Also tried to add the fault document in the descriptor, but not getting the fault in the output.
Any help in this regard will be highly apprciated.
I have attached the package and the wsdl here. In the package, the WSD can be found in the ping folder.
SAG_Issue.zip (22.7 KB)
pingSomething.WSDL (2.91 KB)
#soa#webMethods#API-Management