[Resolved] Namespace and changed endpoint
Hi! I have a situation where we have a new version of a webservice that I would like to use in all out tests. I have defined a new endpoint (the new correct), and changes (in a copy) the endpoint t...
Forum Discussion
SoapUI Pro 4.5.1
I've got exactly the same problem - I need to basically clone my workspace and point at a new version of the webservices.
If I do an update to the definitions, the namespace does not change, either in the PortBindings nor in the test steps and the assertions and property transfers in the test suites. Although the 'Definition Parts' in the port binding overview pane do change correctly.
The url and the version are defined in project level properties, so for example the service endpoint entry looks like:
http://${#Project#ServiceEndpoint}/${#Project#IntegrateVersion}/services/CardService
If I try the refactor definition, I get a dialog saying 'Missing matching binding [{http://blahblahmyUrl/v2_1}CardServicePortBinding] in definition, select new binding to map to and there is a selection box with the {theNewNamespace}CardServicePortBinding
If I select that, soapUI gives me the hourglass, starts consuming hundreds of megabytes of memory ... I let that run for at least 10 minutes and finally decided to kill it. I don't know whether it would ever succeed, but that is ridiculously slow considering I have 18 services in 7 projects that need to be updated.
I can't figure out where the namespace is coming from. I can't find it in any wsdl files.
Obviously it is in the project files I copied, but it seems like there must be someplace where it was originally generated ... be nice to find that point and fix it there.
I don't really want to edit the project file outside soapUI, but its beginning to look like I'll have to
I've got exactly the same problem - I need to basically clone my workspace and point at a new version of the webservices.
If I do an update to the definitions, the namespace does not change, either in the PortBindings nor in the test steps and the assertions and property transfers in the test suites. Although the 'Definition Parts' in the port binding overview pane do change correctly.
The url and the version are defined in project level properties, so for example the service endpoint entry looks like:
http://${#Project#ServiceEndpoint}/${#Project#IntegrateVersion}/services/CardService
If I try the refactor definition, I get a dialog saying 'Missing matching binding [{http://blahblahmyUrl/v2_1}CardServicePortBinding] in definition, select new binding to map to and there is a selection box with the {theNewNamespace}CardServicePortBinding
If I select that, soapUI gives me the hourglass, starts consuming hundreds of megabytes of memory ... I let that run for at least 10 minutes and finally decided to kill it. I don't know whether it would ever succeed, but that is ridiculously slow considering I have 18 services in 7 projects that need to be updated.
I can't figure out where the namespace is coming from. I can't find it in any wsdl files.
Obviously it is in the project files I copied, but it seems like there must be someplace where it was originally generated ... be nice to find that point and fix it there.
I don't really want to edit the project file outside soapUI, but its beginning to look like I'll have to
