I’m trying to set up a web service consumer to connect to the Microsoft Exchange Web Services. I am able to successfully make a call from SoapUI but I’m running into issues trying to do the same in webmethods. I’m getting an error “The request failed schema validation: If the ‘nillable’ attribute is false in the schema, the ‘xsi:nil’ attribute must not be present in the instance.” I was able to reproduce the same error in SoapUI by adding an element to my SOAP request with the xsi:nil attribute = true when that element should not be null according to the schema. Unfortunately the error message from the service contains no specifics about which element is incorrect and I can debug into the generated WS connector but can’t debug into the soap client code (pub.client:soapClient) to see what xml is ultimately being generated and then sent to the service. It seems to me that the integration server is adding in elements that I am not specifying (optional elements) and setting xsi:nil=true. The 8.2 SP1 readme doesn’t specify in which exact situations the IS does this (http://techcommunity.softwareag.com/ecosystem/documentation/webmethods/wmsuites/wmsuite8-2_ga/readme/IntegrationServer_8-2-SP1_readme.pdf see “Modification to control whether SOAP messages distinguish between null and empty elements”), but the behaviour in this case seems odd as it appears to be setting this attribute when the element is not allowed to be null (or perhaps there is something weird going on in the generation of the doc types from the schema). I did try setting the extended setting watt.server.SOAP.generateNilTags to false. This fixed the problem, but I’m leery to flip this setting as our Integration Server hosts multiple packages/projects with various WS calls and I’m not sure what the impact would be on these other services. Is there a way to suppress generation of nil tags on a per-service basis rather than globally?