1) I meant erlsoap, which Chandru uses in his suggestion:
compile_wsdl(Wsdl, Wsdl_erlsoap_config) ->
Header_file_name = filename:basename(Wsdl, ".wsdl") ++ ".hrl",
Model_header_file_name = filename:basename(Wsdl, ".wsdl") ++ "_model.hrl",
Model = erlsoap_lib:initModelFile( <=========== HERE
On Mon, Aug 9, 2010 at 9:15 AM, Tom Hay <email@example.com> wrote:Thanks for digging into this. Questions:
> I finally achieved what I needed, but it was hard work !
> I added a new function yaws_soap_lib:initModelOptions that allows me to pass
> in erlsom options, instead of faking them in yaws_soap_lib:initModel2; also
> a new function yaws_soap_srv:setupOptions that allows me to use the new
> initialisation in the server. That allowed me to pass in a custom
> include_fun that applies the appropriate prefix for the namespaces I'm
> interested in. I'd be happy to contribute the code back to yaws if a
> committer is interested.
> Chandru's suggestion gave me the clues I needed, but I struggled with it a)
> because erlsoap is virtually unobtainable (sources seem to have vanished
> from sourceforge) and b) because yaws scans the wsdl file and automatically
> pulls in the xsd schemas, and doesn't seem to honour the include_files
> options in the config file.
1. Did you mean erlsom, rather than erlsoap? If so, the erlsom sources are here:
2. If there's a problem with include_files in the config file, do you
think it would be preferable to fix that rather than adding new