[Mono-bugs] [Bug 665656] New: SoapReflectionImporter.ImportClassMapping fails to call CheckOptionalValueType after CreateMapMenber (but XmlReflectionImporter.ImportClassMapping does.)

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Wed Jan 19 16:31:46 EST 2011


https://bugzilla.novell.com/show_bug.cgi?id=665656

https://bugzilla.novell.com/show_bug.cgi?id=665656#c0


           Summary: SoapReflectionImporter.ImportClassMapping fails to
                    call CheckOptionalValueType after CreateMapMenber (but
                     XmlReflectionImporter.ImportClassMapping does.)
    Classification: Mono
           Product: Mono: Class Libraries
           Version: 2.8.x
          Platform: 64bit
        OS/Version: Ubuntu
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Sys.XML
        AssignedTo: atsushi at ximian.com
        ReportedBy: ben at skullsquad.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---


User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/534.10
(KHTML, like Gecko) Ubuntu/10.10 Chromium/8.0.552.224 Chrome/8.0.552.224
Safari/534.10

The issue is that when running a compiled SOAP client dll, generated either by
NET or by Mono wsdl, fails to honor optional parameters, as controlled by the
relevant [foo]Specified fields.

It appears that some work was done on this around Feb 2007, as evidenced by
this thread: 

http://www.mail-archive.com/mono-devel-list@lists.ximian.com/msg11567.html

also, a reference in the change log by Atsushi Enomoto on Feb 14, 2007 to a bug
number, #80759 (presumably in this database, but I am not authorized to view
the  ticket.)

I independently arrived at the same patch as in the thread above, which fixes
the issue.

To be clear, without this patch, the SOAP runtime de/ser is completely broken
for us.  The service we are trying to communicate with has many parameters in
their specification that we are not allowed to modify, and must be omitted from
 the calls.  

This works as expected on Windows / .NET.

Reproducible: Always

Steps to Reproduce:
There is a test case in the email thread - I don't see any reason to re-create
one.
Actual Results:  
Optional elements are always sent on the SOAP call.

Expected Results:  
Optional elements should be omitted unless explicitly specified.

I know severity is your busines, not mine.  But this is a major feature of Mono
that is broken, and the second bug I've found in a week with
SoapReflectionImporter.

I consider it a major severity, because it causes a major, advertised feature
of Mono to be fail to function.

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the mono-bugs mailing list