I thought that a Web Service in .NET was only in memory for the time of the transaction. Thus, I assumed that a value defined such as a property of an object was always having its default value for each Web Service hit. But, I found this is not the case. If a property value has been changed in one hit, it remained like that on the second hit. So, I had to force the setting of that property just before calling the method of the object. Can someone explain me a little more on this?
Properties are client side but on the server the object is xml serialized. When you hit the web services a second time the object is deserialized and uses the properties to set the field values.
