On Thursday 09 June 2011, Ron Garret elucidated thus: > I'm new to Soap and Suds so please forgive me if this is a stupid > question. I'm able to connect to a server and access its services > through the RPC interface. The problem I'm having is that the WSDL > I'm dealing with has some "optional" elements that are actually not > really optional but actually have to be left out or the request won't > validate. (There are no valid values, so the element has to be > absent from the request XML.) Is there a way to do that (i.e. > specify that an argument's corresponding XML should be left out of > the request) through the RPC interface? I ran into this problem with the google API. Jeff Ortel pointed me to using a blank string as the element, and it seemed to work. j -- Joshua Kugler Part-Time System Admin/Programmer http://www.eeinternet.com - Fairbanks, AK PGP Key: http://pgp.mit.edu/ ID 0x73B13B6A _______________________________________________ suds mailing list suds(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/suds

Hello, I'm new to Soap and Suds so please forgive me if this is a stupid question. I'm able to connect to a server and access its services through the RPC interface. The problem I'm having is that the WSDL I'm dealing with has some "optional" elements that are actually not really optional but actually have to be left out or the request won't validate. (There are no valid values, so the element has to be absent from the request XML.) Is there a way to do that (i.e. specify that an argument's corresponding XML should be left out of the request) through the RPC interface?