In order to compose several service requests I need to include some *.hrl files generated with soap:wsdl2erlang/1. The problem is that including them in the same module leads to compile errors because of the redefinition of the macro INTERFACE and the records faultdetail, faultcode, faultreasong, soap_fault_1_1, soap_fault_1_2 and qname.
I think it is not very difficult to avoid the problem:
I see the records are available from soap_fault.hrl and soap_wsdl_*.hrl.
Generated macro INTERFACE could include the name of the service in its name: INTERFACE_My_Service.
Generators should take into account that macro INTERFACE changes its name to the proper one.
The only limit, I think, is that qname record is defined in soap_wsdl_1_1.hrl and soap_wsdl_2_0.hrl and the client code should decide on which one to include.
In order to compose several service requests I need to include some *.hrl files generated with soap:wsdl2erlang/1. The problem is that including them in the same module leads to compile errors because of the redefinition of the macro
INTERFACE
and the recordsfaultdetail
,faultcode
,faultreasong
,soap_fault_1_1
,soap_fault_1_2
andqname
.I think it is not very difficult to avoid the problem:
soap_fault.hrl
andsoap_wsdl_*.hrl
.INTERFACE
could include the name of the service in its name:INTERFACE_My_Service
.INTERFACE
changes its name to the proper one.The only limit, I think, is that
qname
record is defined insoap_wsdl_1_1.hrl
andsoap_wsdl_2_0.hrl
and the client code should decide on which one to include.What do you think?
PS. What a nice tool and library! Thanks!