A wish about web service method parameter types.

We were working the other day on interoperation between .Net and Magic. We need to pass string as parameter for a method. The string parameter actually holds XML definitions passes from .Net to Magic and vice versa. Now there is a bug in Magic and XML definition (<? XML …. > ) actually isn’t send to .Net as part of the envelope XML.

 

Due to this problem .Net reject the incoming envelope. But, if we use the <PART> tag of Message to set the Element attribute to XSD definition of complex type every thing works great. Our problem is that the only way to generate such schema from .Net code is just by defining Class with XML tags as fields. It would be more easily and clean if we can use any kind of .Net attributes for setting message part element to complex type inside the schema or external XSD file. After all we can use WebMethod attribute to change Message parameter name but we can’t set Element.

No Comments