You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 31, 2020. It is now read-only.
For now using the Autodiscover feature, thats not possible. Becouse once you define the URI, the same value is set for targetNamespace and soap:address "location".
I would need a way to leave the targetNamespace the same, and only change the soap:adresss location in the <service><port><soap:address></></></>to distinguish between production and test enviroment.
The text was updated successfully, but these errors were encountered:
This issue has been moved from the
zendframework
repository as part of the bug migration program as outlined here - http://framework.zend.com/blog/2016-04-11-issue-closures.htmlOriginal Issue: https://api.github.com/repos/zendframework/zendframework/issues/7552
User: @patrick-hertling
Created On: 2015-05-26T11:24:58Z
Updated At: 2015-11-06T21:54:54Z
Body
A client which developes for .NET enviroment needs the same targetNamespace for the production and test enviroment.
For now using the Autodiscover feature, thats not possible. Becouse once you define the URI, the same value is set for targetNamespace and soap:address "location".
I would need a way to leave the targetNamespace the same, and only change the soap:adresss location in the
<service><port><soap:address></></></>
to distinguish between production and test enviroment.The text was updated successfully, but these errors were encountered: