Passing objects to Web Services 2

yufufi

22y1.7k

I have a class, lets say Message. Added as a reference to both to my web service and client application. A webmethod takes the message class as a parameter. What I want to do is a create an instance in the client application and pass it to the webmethod. I can't do: Message yoyo=new Message(filename); myservice.procMessage(yoyo); .net says I sent Message but what function wants is localhost.Message and cannot cast one to other. Then I tried boxing. But this time: An unhandled exception of type 'System.InvalidOperationException' occurred in system.xml.dll Additional information: There was an error generating the XML document. ---- Then I found the post in the forums. Solution was split your class into 2, data and code. Pass the one with the data. Ok. Then I created a sprMessage class. Sorry. localhost.sprMessage class. localhost.sprMessage ziza=new localhost.sprMessage(); Message yoyo=new Message(filename); yoyo.CopyTo(ziza); Oops. CopyTo wants sprMessage but what I send is localhost.sprMessage which is completely different ?? -- Only solution I can think of now. Instead of sending message class to ProMessage send its data one by one.. [webmethod] promessage(string name,int [] values, ...) ???

7 Replies

Know the answer? Post it — somebody with the same question will find it here.

yufufi22y ago
Thanx a lot, it worked :)
james22y ago
I do recall having Xml Namespace issues when I first developed that type of typecasting. My resolution, which is good practice in any class that you may someday serialize, was to set the namespace of the XmlElement on my base class. When this isn't done, then the namespaces don't match between the local and remote objects [XmlElement(Namespace="http://mynamespace")] public string MyProperty { ... }
yufufi22y ago
I'm sure I'm passing something with value. Here is the code I used to test it: static void Main(string[] args) { localhost.Service1 myservice=new Alltesting.localhost.Service1(); localhost.Class1 zikzak=myservice.getclass(); // it creates a new instance and modifies its string variable (.name) Console.WriteLine("zikzak "+zikzak.name); // it writes the value of the zikzak.name - np // Create Memory Stream System.IO.MemoryStream tmpms = new System.IO.MemoryStream(); // Create XmlSerializer based on remote object System.Xml.Serialization.XmlSerializer tmpxms1 = new System.Xml.Serialization.XmlSerializer(typeof(localhost.Class1)); // Serialize the remote object into the memory stream tmpxms1.Serialize(tmpms, zikzak); // Reset the position of the memory stream so it can be read tmpms.Position = 0; // Create a second XmlSerializer based on the local object System.Xml.Serialization.XmlSerializer tmpxms2 = new System.Xml.Serialization.XmlSerializer(typeof(Library1.Class1)); // Deserialize the memory stream into the local object Library1.Class1 tmpMyObject = (Library1.Class1)tmpxms2.Deserialize(tmpms); Console.WriteLine("tmpMyobject "+tmpMyObject.name); // nothing appears on the screen tmpMyObject.name is empty ?? Console.ReadLine(); }
james22y ago
Were the variables null before you casted them? I pass null values back and forth all the time, and have no problems. Try setting a value to one of your properies in the constructor of your test web service to be sure that you are passing something that contains a value.
yufufi22y ago
Correction: But after deserialization variables are still null.
yufufi22y ago
Thanx but it didn't work for me. I also created a very simple web service and a class to test your method. But after deserialization are still null. So can't do the casting right ??..
james22y ago
Take a look at my code in this post http://216.26.160.137/Forums/AspNetForums20/ShowPost.aspx?PostID=4647 I call this method TypeCasting Through Serialization and it works well to overcome the issue you're having.