Hi Jeff,
fwiw, modifying the wsdl in the way you suggested appears to have
fixed the problem I was having (the wsdl and sample code were in
ticket #64). I made the change below to the wsdl, and it now no longer
throws the TypeNotFound exception (using r507, however 0.3.5 also
works after modifying the wsdl).
--- NSConfig.wsdl.orig 2009-01-12 22:32:37.000000000 +0000
+++ NSConfig.wsdl 2009-05-13 19:58:54.000000000 +0100
@@ -4,6 +4,7 @@
<definitions name="NSConfig" targetNamespace="urn:NSConfig"
xmlns:ns="urn:NSConfig"
<!-- NetScaler-specific simple types -->
The doctor class sounds promising :-)
--Dave
On Wed, May 13, 2009 at 4:58 PM, Jeff Ortel <jortel(a)redhat.com> wrote:
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"/>
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(a)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(a)redhat.com
>>
https://www.redhat.com/mailman/listinfo/fedora-suds-list
>
> _______________________________________________
> fedora-suds-list mailing list
> fedora-suds-list(a)redhat.com
>
https://www.redhat.com/mailman/listinfo/fedora-suds-list
_______________________________________________
fedora-suds-list mailing list
fedora-suds-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-suds-list