wsdl2ruby Ignoring element binding, operation, body, address !

39 views
Skip to first unread message

Ahsan A.

unread,
Jun 6, 2008, 3:49:43 AM6/6/08
to soap4r
Hi all,

I have soap4r 1.5.8 installed as a gem. I need to access an external
soap web service.

So when I generate a client with wsd2ruby, I get the following
message:

ignored attr: {http://www.w3.org/2006/05/addressing/wsdl}Action
ignored element: {http://schemas.xmlsoap.org/wsdl/soap12/}binding
ignored element: {http://schemas.xmlsoap.org/wsdl/soap12/}operation
ignored element: {http://schemas.xmlsoap.org/wsdl/soap12/}body
ignored element: {http://schemas.xmlsoap.org/wsdl/soap12/}address

I get the same message when I try it the other way - loading the wsdl
methods dynamically.

Any ideas ?

wiz21

unread,
Jun 6, 2008, 4:35:20 AM6/6/08
to soap4r
first question is obviously : is the WSDL correct ?

stF

Ahsan A.

unread,
Jun 7, 2008, 1:48:53 AM6/7/08
to soap4r
Yes, the WSDL is correct - Its a web service operated by a commercial
vendor. I tested it in soapui and I can access the service fine.

The service seems to be written in Axis2

Ahsan A.

unread,
Jun 7, 2008, 3:01:55 AM6/7/08
to soap4r
And I should add that creating a client with:

wsdl2ruby --wsdl file.wsdl --type client

outputs defaultDriver.rb with just 3 requirelines, and no class. From
what I've read here: http://markthomas.org/2007/09/12/getting-started-with-soap4r/
there should be a class in that file that is instantiated as a driver.

Any ideas ?

Thanks

On Jun 6, 12:35 pm, wiz21 <stefan.champail...@smals.be> wrote:

Bill Kocik

unread,
Jun 7, 2008, 5:31:02 AM6/7/08
to soap4r
Hi Ahsan -

Just a shot in the dark - this wouldn't happen to be the WSDL for
Google's AdSense API, would it? Because theirs causes these exact
warnings (followed by a fatal error).

Ahsan Ali

unread,
Jun 7, 2008, 5:36:39 AM6/7/08
to soa...@googlegroups.com
Nope :)

Nielsen Bookdata Online.

Is there a way to accomplish a connection by writing everything from scratch ? I wouldn't mind doing that.

Sarah Mei

unread,
Jun 7, 2008, 5:09:13 PM6/7/08
to soa...@googlegroups.com
What directory you're in when you run the script affects the output.

Try running wsdl2ruby.rb from the directory it's installed in, and
giving the full path to the wsdl file (even if wsdl2ruby is in your
path, so you could in theory run it from any directory). Yeah, it's a
little weird. Once I got the right code generated, I tried very hard
to not have to generate it agian. :)

Sarah

Ahsan Ali

unread,
Jun 9, 2008, 1:20:06 AM6/9/08
to soa...@googlegroups.com
Thanks Sarah, but that didn't work ...

However, I did find a solution - kind of :)

I googled and discovered that soap4r does not support soap1.2, and my wsdl file has support for both 1.1 and 1.2, so it has two separate binding, and port elements for each, as well as a soap12 namespace.

Look at the output again - it means 'soap12'I manually removed all elements under the soap12 namespace, and now I get a generated class in defaultDriver.rb.

However, I still get this warning: ignored attr: {http://www.w3.org/2006/05/addressing/wsdl}Action

Any ideas ?
Reply all
Reply to author
Forward
0 new messages