InventoryLocato
15 years agoContributor
When Updating Definition do not
update Name.
In my organization, we have two webservices that are named the same but have different functions (one goes to mainframe other goes to oracle).
When adding them by default, they have the name of blahDefaultbinding (both of them do). when I go to update definition, it updates the name and complains that I have two of them. I started getting rid of the duplicate and realized what had happened. I am not a happy camper. DON'T UPDATE THE NAME! UPDATE THE ENDPOINTS!
In my organization, we have two webservices that are named the same but have different functions (one goes to mainframe other goes to oracle).
When adding them by default, they have the name of blahDefaultbinding (both of them do). when I go to update definition, it updates the name and complains that I have two of them. I started getting rid of the duplicate and realized what had happened. I am not a happy camper. DON'T UPDATE THE NAME! UPDATE THE ENDPOINTS!