Posted: Wed Sep 17, 2014 9:10 am Post subject: XMLNSC syntax checker for an invalid reference
Newbie
Joined: 22 Sep 2011 Posts: 5
I have a wsdl from a partner they have changed the output parameters on the output ex: ns:HelloResponse.ns:Responsev1 to ns:HelloResponse.ns:Responsev2. They made a lot of changes to elements in the output. I am trying to find a way to see if syntax checker helps me out with invalid references(ex: ns:HelloResponse.ns:Responsev1 is invalid after the upgrade to new version).
The current message flow we have uses soap extract and reads the response from LocalEnvironment using XMLNSC. I imported the new WSDL and created messageset but the syntax checker in broker doesn't error if I use older elements(ex: ns:HelloResponse.ns:Responsev1). If I change the reference to SOAP from XMLNSC it validates and shows as a syntax error. I also tried to change the mset file to use XMLNSC but still doesnt validate it. I am using 7.0.0.3 broker toolkit.
Have you restarted your toolkit with -clean? That might cause the errors to be reported in the ESQL editor.
Stating the obvious here, but you should not be relying on the toolkit to find this type of problem ( not saying that you *are* doing so ). You should have automated tests that are executed whenever any change is made. _________________ Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum