Re: Found unrecognised attribute in SOAP WSD

It looks like something in your code is trying to do something that SOAP::WSDL doesn't like. If you get a stack trace, it should show you where in your code the problem is. Put the following under your other use statements:

use Carp;
$SIG{__DIE__} = sub {confess "@_";};
$SIG{__WARN__} = sub {confess "@_";};
[download]

I don't have SOAP::WSDL installed, so I can't run this myself. The error message should help you track the problem down.

Update: carp changed to Carp. Thanks Anonymous Monk!

Comment on Re: Found unrecognised attribute in SOAP WSD Select or Download Code

Replies are listed 'Best First'.
Re^2: Found unrecognised attribute in SOAP WSD by Anonymous Monk on Aug 06, 2013 at 07:12 UTC
There is no "carp" module :) `use Carp::Always;` is shorter to type	[reply]
Re^3: Found unrecognised attribute in SOAP WSD by nevdka (Pilgrim) on Aug 06, 2013 at 11:32 UTC
Yes, it should have been `use Carp;`. It's not the first time I missed that capital, and I doubt it will be the last. :) I didn't know about `Carp::Always`, but it sounds useful. Thanks!	[reply] [d/l] [select]
Re^3: Found unrecognised attribute in SOAP WSD by ebs_perl (Initiate) on Aug 06, 2013 at 21:36 UTC
Hi, I've got the same problem. Did you get a solution for the error? Are you trying to use a web service that is hosted by an IBM i machine (aka, AS400)? Please, let me know if you found a solution, it would help me so much. Thank you, Esdras	[reply]
Re^4: Found unrecognised attribute in SOAP WSD by Anonymous Monk on Aug 06, 2013 at 23:47 UTC
Hi, I've got the same problem. Did you get a solution for the error? Are you trying to use a web service that is hosted by an IBM i machine (aka, AS400)? Please, let me know if you found a solution, it would help me so much. Thank you, Esdras nevdka didn't ask the question, so the chances of nevdka finding the solution are slim to nine. nevdka volunteered a debugging tip for the OP to use, you can use this tip too Like the OP, you're not providing enough details for anyone to begin to answer the question: is this bug in WSDL(a detail) or bug in SOAP::WSDL You could try SOAP::Simple or another client (or some kind of soapspy... xmllint...) to see how they handle the source WSDL, if they detect problems with it like SOAP::WSDL does My soap tips (I hate soap), SOAP::Lite is too much work, SOAP::Simple is less work (but its simple, when stuck go to XML::Compile::SOAP, more verbose, but you want verbose with SOAP ) ... its built on XML::Compile::SOAP/http://perl.overmeer.net/xml-compile/#doc , see my treasure trove of soap examples and lost knowledge,$soap->transport->add_handler("request_send", \&pp_dump );, http://cookbook.soaplite.com/, SOAP endpoint , Re^3: SOAP::Lite login setup, Re: I do not understand how to write a SOAP server., An XML Overview Towards Understanding SOAP, Re^3: SOAP::Lite and custom envelopes, The XML FIles: Understanding XML Namespaces, How to Call a .NET-based Web Service Using the SOAP::Lite Perl Library (don't use XML::Compile )	[reply]