Using the soap header is a good idea if you can be sure that the client knows what soap is. Correct? If you're trying to make the response available to a wide range of clients is this a good idea?
I haven't researched this in detail but I appear to be having issues with serialization of the Exception type. If I let the framwork handle the exception it automatically converts the Exception to a SoapException (and back to a .net Exception if the client is .net) However, when I try to stick the Exception type in my container I get serialization errors. I'm not, as yet, sure why or really if I should be trying to do this at all. =================================== This list is hosted by DevelopMentor� http://www.develop.com Some .NET courses you may be interested in: Essential .NET: building applications and components with CSharp August 30 - September 3, in Los Angeles http://www.develop.com/courses/edotnet View archives and manage your subscription(s) at http://discuss.develop.com
