Hi,

We have a SOAP server created with "SOAP::Transport::HTTP::Server->new();", however for some reason it doesn't reply with the same namespace as the SOAP request.

For example if we get request:
<q1:get_my_person xmlns:q1="http://127.0.0.1/Our/API">...</q1:get_my_person>

Then I think we should reply with:
<q1:get_my_personResponse xmlns:q1="http://127.0.0.1/Our/API">...</q1:get_my_personResponse>

But we actually reply:
<get_my_personResponse xmlns="http://127.0.0.1/Our/API">...</get_my_personResponse>

Am I right in what I think? Anyone know how to make SOAP::Transport::HTTP::Server reply with the namespace provided by the client?
BTW, the namespace seems to be an issue because Visual Studio client won't recognise the result without the namespace it provided. Any advice on Visual Studio specific issues also welcome.
Thanks!

In reply to SOAP reply with correct namespace by dcunningham

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.