I solved this problem myself.
I specified the name space (xmlns) in the serialized XML.
So that the name spaces agreed.
/Erik
snowie
Last Activity: Aug 23 '06, 04:28 PM
Joined: Aug 8 '06
Location:
-
snowie replied to Deserialization problem --> InvalidOperationException "obect xmlns=> was not expectedin ASP ClassicLast edited by Niheel; Aug 25 '06, 05:24 AM. -
Web service subcription model
I am currentlly developing a web service. Right now I use the traditional request/response model. I would, however, like to use a subscription based model.
Is that possible using .NET 2.0 ?
I have seen solutions with a web service on both ends. The client itself implements a web service for the web service (server) to send data to. I do not like this solution though. The client should be easy to deploy and anyone should... -
snowie started a topic Deserialization problem --> InvalidOperationException "obect xmlns=> was not expectedin ASP ClassicDeserialization problem --> InvalidOperationException "obect xmlns=> was not expected
I have a simillar problem to what others have had before me. I just can't find the solution in any earlier post here at the scripts (or any other forum).
I am calling a web service that returns a string, the string is an object serialized into XML. The XML returned could look like:
...Code:<object><name>Safir.Vehicles.Vehicle</name><instance>0</instance><members><member><name>Callsign</name><value></value></member><member><name>Identity</name><value>Safir.Vehicles.Enum.Identity.Friend</value></member><member><name>Transient</name></member><member><name>VehicleID</name><value></value></member></members></object>
Last edited by Niheel; Aug 25 '06, 05:24 AM.
No activity results to display
Leave a comment: