Please do not reply to this email- if you want to comment on the bug, go to the URL shown below and enter your comments there.
Changed by [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=82249 --- shadow/82249 2007-07-31 08:20:46.000000000 -0400 +++ shadow/82249.tmp.23788 2007-07-31 08:20:46.000000000 -0400 @@ -0,0 +1,84 @@ +Bug#: 82249 +Product: Mono: Class Libraries +Version: 1.2 +OS: +OS Details: +Status: NEW +Resolution: +Severity: +Priority: Major +Component: Sys.XML +AssignedTo: [EMAIL PROTECTED] +ReportedBy: [EMAIL PROTECTED] +QAContact: [EMAIL PROTECTED] +TargetMilestone: --- +URL: +Cc: +Summary: Serializer produces duplicate ids for SOAP:Header and SOAP:Body content + +Description of Problem: + +When trying to pass a complex structure to the SOAP server the Serializer +produces duplicating ids for content that is included to SOAP:Header and +SOAP:Body + +Steps to reproduce the problem: +1. Compile the code attached +2. Start the SOAP server (perl version will be attached as well) +3. Run IdIssue.exe and watch the produced XML to appear at the stdout of +server.pl + +Actual Results: +<?xml version="1.0" encoding="utf-8"?> +<soap:Envelope xmlns:xsi="[...]" xmlns:xsd="[...]" xmlns:soap="[...]"> + <soap:Header> + <AuthInfo href="#id1" /> + <q1:AuthInfo id="--> id1 <--" xsi:type="q1:AuthInfo" xmlns:q1="[...]"> + <session_id xsi:type="xsd:string">Some Session ID</session_id> + </q1:AuthInfo> + </soap:Header> + <soap:Body soap:encodingStyle="[...]"> + <q1:GetString xmlns:q1="[...]"> + <obj href="#id1" /> + </q1:GetString> + <q2:Array id="--> id1 <---" q2:arrayType="xsd:anyType[2]" xmlns:q2="[...]"> + <Item xsi:type="xsd:int">123</Item> + <Item xsi:type="xsd:string">string123</Item> + </q2:Array> + </soap:Body> +</soap:Envelope> + + +Expected Results: +The ids marked by "-->" and "<---" should be different as they should be +unique across the Envelope. + +How often does this happen? +Always + +Additional Information: +When the server receives such markup it starts referring to <q2:Array> as +<AuthInfo> structure and fails to process the session_id. I guess the +behaviour cannot be predicted in such case. + +Microsoft.NET version of the request is below - headers have h_ appended to +the ids and Body contains plain ids + +<?xml version="1.0" encoding="utf-8"?> +<soap:Envelope xmlns:soap="[...]" xmlns:soapenc="[...]" xmlns:tns="[...]" +xmlns:types="[...]" xmlns:xsi="[...]" xmlns:xsd="[...]"> +<soap:Header> + <types:AuthInfo id="h_id1"> + <session_id xsi:type="xsd:string">Some Session ID</session_id> + </types:AuthInfo> +</soap:Header> +<soap:Body soap:encodingStyle="[...]"> + <tns:GetString> + <obj href="#id1" /> + </tns:GetString> + <soapenc:Array id="id1" soapenc:arrayType="xsd:anyType[2]"> + <Item xsi:type="xsd:int">123</Item> + <Item xsi:type="xsd:string">string123</Item> + </soapenc:Array> +</soap:Body> +</soap:Envelope> _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
