comment on

At this stage however, I am unsure whether this is an issue with my WSDL file or the limited WSDL 1.1 support offered by SOAP::Lite

Following some further reading of the WSDL specification (1.1, http://www.w3.org/TR/wsdl), it appears that additional SOAP headers should be able to be specified without these headers necessarily needing to be specified within the WSDL file - "It is not necessary to exhaustively list all headers that appear in the SOAP Envelope using soap:header. For example, extensions (see section 2.1.3) to WSDL may imply specific headers should be added to the actual payload and it is not required to list those headers here.".

To this end, I tested removing the <soap:header> definition from the private_method binding in the WSDL (in case the problem was being caused by an error in my WSDL definition) to no avail.

Anyone else got any other ideas short of diving into the source of SOAP::Lite?

perl -le "print unpack'N', pack'B32', '00000000000000000000001011001001'"

In reply to Re: SOAP Headers, WSDL and SOAP::Lite by rob_au
in thread SOAP Headers, WSDL and SOAP::Lite by rob_au

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


laziness, impatience, and hubris
	PerlMonks