Does anyone Have any experience in creating a webservice client on Integration Server without using a WS Descriptor generated through designer. The reason I ask is while I understand the reason SAG is eliminating some of the service that allow for more custom flexibility, we do have some issues with the descriptors and want to find some options.
- The auto-created WSD consumer creates too many nested document types that really slows down our automated CI deployments.
- The auto-created WSD consumer creates documents named with the namespace pulled form the WSDL schema. The problem is that our applications auto generate WSDLs and that namespace can change. If that happens our WSD breaks.
So my thought is to create a custom WS client that limits these two problems but still follows the basic principals of SOAP standards. I wanted to use the service wm.pub.client:soapClient but I am struggling with the “wsdname” input, it is required but I cannot seem to find out what exactly needs to be used here (wsdl address does not work). Somehow the auto-generated descriptors pass that wsdname hidden from the pipeline.
Anyone with some examples of how to use pub.client:soapClient or some advice on building a custom WS client. Also any suggestions on how to fix our issues using the standard descriptors generated by designer would help too.
BTW. we are still on version 8.2 (so maybe it get’s better with 9x?)