Hi Jeff,<div><br></div><div>This discussion has brought back a couple of thoughts I had when I started using Suds.</div><div><ul><li>Would it not be possible to load the WSDL from a string ?</li><li>Would it not be possible to load the "cache" also from a string/file (or even remove the cache concept)?</li>
</ul><div>Although I am sure that the "cache" concept has uses for some people, I feel that most people use the client against invariant WSDL files and therefore have no need for a "cache" concept, but for a pre-generated version.</div>
<div><br></div><div>This may open the door to having an independent tool to pre-generate the "cache" with the WSDL file and then let people have a client that works (with the same API as today) by loading that "cache" (call it: "pre-generated set of objects") instead of referencing the WSDL.</div>
<div><br></div><div>Best regards</div><div><br></div><div><br></div><div class="gmail_quote">On Tue, Nov 24, 2009 at 15:05, Jeff Ortel <span dir="ltr"><<a href="mailto:jortel@redhat.com">jortel@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hey Elyrwen,<br>
<br>
If the wsdl is self contained (it does not import anything) I'd suggest you download the wsdl and then use suds to parse the local file as:<br>
<br>
><br>
> url = 'file:///home/edynesh/wsdl.xml'<br>
> client = Client(url)<br>
><br>
<br>
Otherwise, you can do as you suggested and let suds resolve the dependencies and rely on the cache to store the files locally. Or, you can read the wsdl and manually download all of the dependencies as well.<br>
<br>
On 11/24/2009 05:22 AM, Elyrwen Dynesh wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello,<br>
<br>
I need to use suds to parse a wsdl available on my local network,<br>
however there is no connection<br>
to the internet. Port 80 is blocked in and out. What are my options? So<br>
far, I was thinking about the following solutions:<br>
<br>
1. Unblock 80 and let suds parse the wsdl and create the schemas in<br>
/tmp/suds. Then block 80 and use suds normally. This seems to work,<br>
however I don't know how long? Is there any caching<br>
</blockquote>
<br>
Yes, you can do this. By default, suds caches files in /tmp/suds for 1 day. You can change this by doing something like:<br>
<br>
><br>
> client.options.cache.setduration(days=0) # 0 = forever<br>
><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
fedora-suds-list mailing list<br>
<a href="mailto:fedora-suds-list@redhat.com" target="_blank">fedora-suds-list@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/fedora-suds-list" target="_blank">https://www.redhat.com/mailman/listinfo/fedora-suds-list</a><br>
</blockquote>
<br>
<br>_______________________________________________<br>
fedora-suds-list mailing list<br>
<a href="mailto:fedora-suds-list@redhat.com">fedora-suds-list@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/fedora-suds-list" target="_blank">https://www.redhat.com/mailman/listinfo/fedora-suds-list</a><br></blockquote></div><br></div>