By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
432,027 Members | 1,088 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 432,027 IT Pros & Developers. It's quick & easy.

SOAP serialization of nullable types and remoting - not supported?

P: n/a
Hello,

I have recently stumbled upon a problem with serialization of nullable
value types in .Net 2.0 and would appreciate any explanation of what's
happening. My application is hosted in IIS and exposes a web service
with nullable data types - like:
public class DataItem {
DateTime? Timestamp;
int? SomeData;
}
Web service's WSDL correctly specifies that the nullable fields are
'nillable' in the xml schema, and everything works fine (clients are
able to correctly call the web service). Problem starts when I want to
pass the same data through remoting. The web service communicates by
remoting with another application, also hosted in IIS. So, naturally,
I'm using soap formatter for remoting. Unfortunately, this combination
doesn't work - application throws an error with message saying that
nullable type serialization is not supported in soap formatter. WTF?
Web service uses SOAP and everything is fine. SOAP formatter also uses
SOAP, so why does it refuse to handle nullable values? Is some other
'SOAP' used for remoting, and if so, can someone explain why?

Best regards
Rafal Gwizdala

Sep 26 '07 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.