Announcement

Collapse

Mirth Connect 3.12.0 Released!

Mirth Connect 3.12.0 is now available as an appliance update and on our GitHub page. This release includes database performance improvements, improves visual HL7 representation, message pruning, keystore handling, PDF generation, community contributions, and fixes several security vulnerabilities. This release also contains many improvements to commercial extensions. See the release notes for the list of fixes and updates.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

WS: Use of undefined namespace prefix

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • WS: Use of undefined namespace prefix

    Hi everyone!

    I'm having trouble invoking Web Services on Mirth.
    I want to use a transformer so I can work build the SOAP Envelope dinammically (the automatic SOAP Envelope generator isn't working for me).
    When I use the transformer I get the following error:

    Code:
    TypeError: error: Use of undefined namespace prefix: soapenv
    I've tried to remove the namespaces but the web services provider reject that ("Version mismatch").

    My correct SOAP Envelope is:

    Code:
    <soapenv:Envelope xmlns:«»soapenv="[url]http://schemas.xmlsoap.org/soap/envelope/"[/url] xmlns:«»siim="[url]http://xpto.pt"[/url] xmlns:«»xsd="[url]http://types.xpto.pt/xsd">[/url]
       <soapenv:Header/>
       <soapenv:Body>
          <siim:novaRequisicao>
             <siim:idReqExterno>?</siim:idReqExterno>
             <siim:doente>
                <xsd:dtaNasc>?</xsd:dtaNasc>
                <xsd:id>?</xsd:id>
                <xsd:idExterno>?</xsd:idExterno>
             </siim:doente>
          </siim:novaRequisicao>
       </soapenv:Body>
    </soapenv:Envelope>
    Can anyone help. I'm completely stuck.

  • #2
    Re:WS: Use of undefined namespace prefix

    I'm not sure if this is the issue, but I remember having to alter the envelope to access ours as well. One difference I see is that I have the following:

    <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <soap:Body soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">

    Where I'm including the soapenc url. I hope this helps.

    Kerry

    Comment


    • #3
      Has anyone figured out how to do this? I have the same problem with a SOAP message I am getting from a vendor.

      Comment

      Working...
      X