- This topic has 7 replies, 3 voices, and was last updated 9 years, 5 months ago by
.
-
Posts
-
We have a number of SOAP services that we have been using and generating in ME 10.7 for years. We are trying to move to ME 2015, but it is generating the wrong address for the services.
The section appears at the bottom of the WSDL and here are the two versions:
Generated ME 10.7 service configuration in WSDL file:
<service name=”OFSiteSrvcService”>
<port binding=”tns:OFSiteSrvcPortBinding” name=”OFSiteSrvcPort”>
<soap:address location=”http://localhost:8080/OF-WsMain/OFSiteSrvcPort”/>
</port>
</service>Generated ME 2015 service configuration in WSDL file:
<service name=”OFSiteSrvcService”>
<port binding=”tns:OFSiteSrvcPortBinding” name=”OFSiteSrvcPort”>
<soap:address location=”http://localhost:8080/OF-WsMain/OFSiteSrvcService”/>
</port>
</service>The difference is on the soap:address, the 10.7 format works with both running versions, the one generated on 2015 does not work when it is hit by a service client.
As far as I can find, there are no preferences to set, the options selected for running the bottom-up generation are the same, and I cannot find anything to alter what ME 2015 is doing.
Anyone have any info on what might be causing this?
Thanks
mongonv,
Thank you for pointing to this issue. We could replicate the issue at our end. The soap:address should use the Port name instead.The dev team is working on it.
As a workaround, please replace the generated WSDL with the one supplied by the service after deployment.
Sorry for inconvenience caused.
mongonv,
As Swapna said, we’re working on a fix for this for the next release. Do let us know of any other problems you have found migrating to 2015.
Swapna,
We are the ones generating the web service so there is no other wsdl to replace it with, that is why its an important issue.With this bug, we will have to edit the generated wsdl’s after every change, so we hope that a fix will be available very soon.
Thanks
Any word on when this fix will be getting completed?
Having to edit the wsdl on every generation is very annoying to say the least.
Ed,
Apologies, we have already fixed this and it will be in the next release. We’re stuck on the last few issues and it should be available early next week.
