No announcement yet.

Incoming SOAP wrapper from Oracle SOA

  • Filter
  • Time
  • Show
Clear All
new posts

  • Incoming SOAP wrapper from Oracle SOA

    I've been debugging incoming SOAP messages (coming to the SOAP listener, in Mirth Connect 2.2.1) coming to us from Oracle SOA Suite.

    They fail with two problems in the SOAP wrapper:

    1) No "arg0": the acceptMessage node apparently needs to have the actual payload inside an "arg0" node or it won't be found.

    2) namespaces: Oracle SOA submits the "acceptMessage" like this:
    <acceptMessage xmlns="">
    but that fails; instead I have to do this before the message is accepted:
    <test:acceptMessage xmlns:test="">
    These aren't major variations, but because Mirth is fairly rigid about the wrapper, we're rejecting these messages.

    Is there better support for SOAP integration in later Mirth versions? It seems quite valuable to me for Mirth Connect to be able to accept the auto-generated SOAP wrappers (based on Mirth's WSDL) that other major integration tools generate.

    Kind regards,
    Last edited by rwhelan; 07-07-2014, 04:21 AM. Reason: use standard Mirth namespace

  • #2
    Yes, in fact in 3.1 we're building in some new features to the HTTP Listener so that you can emulate a SOAP web service and do literally whatever you want. You'll be able to host static resources like WSDLs/XSDs, and then accept any request (regardless of the specific XML formatting), and do your own custom validation in a filter or transformer.
    Step 1: JAVA CACHE...DID YOU CLEAR ...wait, ding dong the witch is dead?

    Nicholas Rupley
    Work: 949-237-6069
    Always include what Mirth Connect version you're working with. Also include (if applicable) the code you're using and full stacktraces for errors (use CODE tags). Posting your entire channel is helpful as well; make sure to scrub any PHI/passwords first.

    - How do I foo?
    - You just bar.