[WebService(Name space="http://production/myWebService.as mx")]
//[WebService(Name space="http://test/myWebService.as mx")]
//[WebService Namespace="http ://development/myWebService.as mx")]
public class myWebService: System.Web.Serv ices.WebService
{
....
}
In the above example, what is the best practice in setting up a webservice
namespace in an environment where 1 webservice is published in a 3-tiered
architecture (dev-test-prod). I understand that the namespace does not need
to be an actual url, so would it be best just to pick one url and be
consistent for each deployment, such as
//[WebService Namespace="http ://webservices.com pany.com/myWebService.as mx")]
//[WebService(Name space="http://test/myWebService.as mx")]
//[WebService Namespace="http ://development/myWebService.as mx")]
public class myWebService: System.Web.Serv ices.WebService
{
....
}
In the above example, what is the best practice in setting up a webservice
namespace in an environment where 1 webservice is published in a 3-tiered
architecture (dev-test-prod). I understand that the namespace does not need
to be an actual url, so would it be best just to pick one url and be
consistent for each deployment, such as
//[WebService Namespace="http ://webservices.com pany.com/myWebService.as mx")]