|
|
| Author |
Message |
< Yaws mailing list ~ yaws_soap_lib and import statements |
| Guest |
 Posted: Fri Sep 21, 2007 2:52 pm |
 |
|
|
Guest
|
Hi,
I am trying to do an initModel call like
yaws_soap_lib:initModel("file:///home/mikael/tmp/SilDB2.4.wsdl")
on a wsdl file that has a import element to an URL in
its schema section:
<import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
I get:
{{badmatch,{error,"Include file not found (undefined)"}}...
I know that erlsom should be able to handle "external" schemas, but I
do not know how to pass the right options to yaws_soap_lib for this.
Does anone know how to deal with this? It ought to be a quite common
statement in wsdl (and schema) files.
Thanks
Mikael Karlsson
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Erlyaws-list mailing list
Erlyaws-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/erlyaws-list
Post recived from mailinglist |
|
|
| Back to top |
|
| Willem |
| Posted: Fri Sep 21, 2007 4:23 pm |
|
|
|
User
Joined: 21 Jul 2006
Posts: 59
|
|
| Back to top |
 
|
| Guest |
| Posted: Fri Sep 21, 2007 4:46 pm |
|
|
|
Guest
|
Thanks Willem,
downloading the xsd and importing with the schemaLocation did the trick
(could not use http://... in schemaLocation though):
<import namespace="http://schemas.xmlsoap.org/soap/encoding/"
schemaLocation="/home/mikael/tmp/encoding.xsd" />
As you pointed out the service uses soap encoding, and I did not read
the yaws_soap_lib manual properly before starting...not the first time...
As this service is an external one, the wsdl is not generated by me. I
guess I will have to revert to some other solution like Java and Axis, or
is there any workaround if I was to use erlsom directly?
Best regards
Mikael
On Friday 21 September 2007 18:22:49 Willem de Jong wrote:
> Hi Mikael,
>
> I don't think it is really possible at the moment. Erlsom has some options
> to tell it where to look for imports, but they are not taken into account
> by the code in yaws_soap_lib.
>
> I am planning a new release for this code, and I will try to solve it with
> that release.
>
> In the mean time, the easiest solution/work around is to include a
> 'schemaLocation' attribute in the import statement:
>
> <import namespace=*"*http://schemas.xmlsoap.org/soap/encoding/"
> schemaLocation=*"*http://schemas.xmlsoap.org/soap/encoding/"/>
>
> However, this import seems to imply that your service is using soap
> encoding. This is not supported by yaws soap, only 'document-literal' is
> supported.
>
> If you generated the WSDL using a tool like Axis java2wsdl, you can try to
> change the settings in such a way that it generates document literal type
> of services.
>
> Good luck,
> Willem
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Erlyaws-list mailing list
Erlyaws-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/erlyaws-list
Post recived from mailinglist |
|
|
| Back to top |
|
| Willem |
| Posted: Fri Sep 21, 2007 6:25 pm |
|
|
|
User
Joined: 21 Jul 2006
Posts: 59
|
|
| Back to top |
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
