Forum Discussion
4 Replies
- nmrao
Champion Level 2
I would suggest to check with your team or service provider to find if there is any change in the wsdl definition.
Tool can't imagine the schema and add random data to the request.- richieCommunity Hero
Hi MRutten
Just reiterating what Rao and msiadak mentioned.
There is a switch to add in all optional tags from a schema. If your schema is embedded within your .wsdl (and it sounds like thats the way its been setup) and this switch has been set then I'm almost 100% positive this will be the cause (unless a regression has been added to v3.2!) as the content added is too non random to be anything else.
you could always double check by extracting the .xsd from the .wsdl, launch in something like XMLSpy and use XMLSpy to generate an example xml instance based on the .xsd content (XMLSpy also includes switches to build instance content with and without optional tags/attributes
cheers,
rich
- groovyguyCommunity Hero
I haven't made the upgrade from 2.3.0 to 3.1.0 yet, but the only time I've seen this behavior is if I have ReadyAPI set to automatically build requests with optional fields and use the F5 / Recreate request buttons to rebuild the request.
Hi MRutten, let's see if the community members faced anything similar and have advice on how to handle this.
Any idea of what could be happening?
nmrao HimanshuTayal richie groovyguy
Thanks!