Hi,
I'm currenty trying to debug a soap error where the ruby lib savon uses the wrong namespace for soap request elements, if these elements are part of a choice in the wsdl. Actually, savon does not parse the wsdl by itself, but uses wasabi, and then does not find the element in wasabis list of type definitions and namespaces.
Example:
wsdl = Wasabi::Document.new('https://tom.vgwort.de/services/1.0/authorMessageService.wsdl')
then most elements defined in this wsdl can be found in
wsdl.type_definitions or
wsdl.type_namespaces
except for those within choices, i.e. the elements pdf, plainText, and epub in the given example. Since savon can't find them in the list, it uses the wrong namespaces.
wasabi doesn't seem to cope at all with choice elements, although it is a valid xml schema element:
https://www.w3schools.com/xml/el_choice.asp
regards
Hadmut
Hi,
I'm currenty trying to debug a soap error where the ruby lib savon uses the wrong namespace for soap request elements, if these elements are part of a choice in the wsdl. Actually, savon does not parse the wsdl by itself, but uses wasabi, and then does not find the element in wasabis list of type definitions and namespaces.
Example:
wsdl = Wasabi::Document.new('https://tom.vgwort.de/services/1.0/authorMessageService.wsdl')
then most elements defined in this wsdl can be found in
wsdl.type_definitions or
wsdl.type_namespaces
except for those within choices, i.e. the elements pdf, plainText, and epub in the given example. Since savon can't find them in the list, it uses the wrong namespaces.
wasabi doesn't seem to cope at all with choice elements, although it is a valid xml schema element:
https://www.w3schools.com/xml/el_choice.asp
regards
Hadmut