The XML-schema standard specifies that the schema attribute "elementFormDefault" controls whether all elements need a namespace (elementFormDefault="qualidied") or whether only top level elements need a namespace and contained elements must not have a namespace (elementFormDefault="unqualified").
Apparently, ZSI 2.0 treats "elementFormDefault='unqualified'" (the default) incorrectly.
Logged In: YES
user_id=711996
Originator: NO
You need to include the parts of the WSDL/schema and the XML instances in question in your bug report.
There are already many unittests that test unqualified element form, and ZSI handles both qualified and unqualified.
This probably boils down to is your case/bug not covered by the unittests, or is your diagnosis faulty.
WSDL causing the problem
Logged In: YES
user_id=265829
Originator: YES
WSDL file attached.
Instance sent by server:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header/>
<SOAP:Body>
<ns0:WS_TI_Status_Response xmlns:ns0="http://haufemg.com/xi/ecom/osp/sws/ws_ti_status">
<Header>
<KundenNr>0094037216</KundenNr>
<TicketNr>HSC000000197775</TicketNr>
<Authentifiziert>Y</Authentifiziert>
</Header>
<TicketDaten>
<TicketNr>HSC000000171344</TicketNr>
<Produktname>Lohn+Gehalt pro</Produktname>
<Bereich>Installation / Deinstallation</Bereich>
<Ticketstatus>Weitergeleitet</Ticketstatus>
<Ticketstatus_Attribut/>
</TicketDaten>
File Added: XD1_WS_Get_TI_Status.wsdl
Logged In: YES
user_id=711996
Originator: NO
Fix is in.
$ svn log -r1440
------------------------------------------------------------------------
r1440 | boverhof | 2008-01-10 17:26:39 -0800 (Thu, 10 Jan 2008) | 9 lines
M test/wsdl2py/config.txt
M test/wsdl2py/wsdl/test_Unqualified.xsd
M test/wsdl2py/test_Unqualified.py
M ZSI/generate/containers.py
-- [ 1853368 ] "elementFormDefault='unqualified'" mishandled
This bug caused local element declarations to be incorrectly namespaced. Appears to belimited to local element declarations with local type definitions (both simpleType and complexType), both these scenarios are fixed now with unittests.
------------------------------------------------------------------------
Logged In: YES
user_id=1315684
Originator: NO
I can confirm this works for me now.
Logged In: YES
user_id=1312539
Originator: NO
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).