Tom,
I'm assuming that the @ref="s:schema" is referencing the <schema/> element in the schema for XSD itself (http://www.w3.org/2001/XMLSchema.xsd) and that the content of the referencing element is XSD content.
The best workaround at the moment is to add: <s:import namespace="http://www.w3.org/2001/XMLSchema%22/%3E To the schema contained in the wsdl. This is missing which causes the schema to be broken.
I committed a patch to: - Statically bind the schemaLocation for the http://www.w3.org/2001/XMLSchema namespace. - Update the sax parser so it will not follow the bogus DTD reference in XSD schema.
So, you'll need r507+ or the latest 0.3.6 beta release.
Does this work for you?
I have started working on a schema /Doctor/ class that will fix broken schemas like this one and others I've come across. But it will probably be a few weeks getting into the code base. The Doctor will be extensible so users can plug in additional fixes.
Regards,
Jeff
Tom von Schwerdtner wrote:
Actually my real problem may be #8 (https://fedorahosted.org/suds/ticket/8) since the service I'm calling seems to use ref="s:schema", or at least that's my current theory. The xml in question is here: http://civicit.com/~tvon/problematic-wsdl.xml
I could use any advice on working around this or ideas on implementing the required changes in suds (I'm a handy Pythoner, but not at all familiar with suds or xml processing) as I'm on a bit of a deadline and need to get this worked out.
-Tom
On Tue, 12 May 2009 19:58:39 +0000, Tom von Schwerdtner tomvons@gmail.com wrote:
Does anyone know of a work-around for this, or have ideas on how to solve it?
Also, how do I get an account in the Trac site to get on the CC list for this bug?
Thanks, Tom
fedora-suds-list mailing list fedora-suds-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-suds-list
fedora-suds-list mailing list fedora-suds-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-suds-list