Open rbeckman-nextgen opened 4 years ago
There's already MIRTH-3834 for the Web Service Listener side of things.
But regarding the HTTP Listener, [~dans] can you explain why exactly MTOM isn't supported? The HTTP Listener supports virtually any kind of request, including multipart ones. As of 3.1 and later, it can also automatically parse multipart messages into nested XML structures, making traversal of complex requests easy. Is there some nuance to MTOM that isn't possible to handle with the HTTP Listener?
Imported Comment. Original Details: Author: narupley Created: 2015-11-17T10:46:27.000-0800
I was more concerned about responding with an MTOM message.
Imported Comment. Original Details: Author: dans Created: 2015-11-17T10:50:04.000-0800
Can you elaborate more on that then? When it comes down to it, it's really just a multipart payload, which is possible to send as a response from the HTTP Listener. Granted, you have to generate the payload and boundary information, but that's it.
How are you envisioning this as a feature in MC? What sort of configurable options would you want/need?
Imported Comment. Original Details: Author: narupley Created: 2015-11-17T11:41:03.000-0800
Maybe there is a better way of doing this. I am trying to use MC as proxy for XDSb calls. i want to be able to intercept WS calls from/to Mirth Results. I want to be able to pass the response from the destination as is including all headers.
Right now I have it setup as a HTTP listener with a WS sender. It gets a bit tricky to set the response content type. Is there a better way of doing this?
Imported Comment. Original Details: Author: dans Created: 2015-11-17T12:09:38.000-0800
Add support for MTOM on the HTTP Listener (and possibly WS Listener).
This would enable more flexibility to use Mirth Connect as a XDS.b/NwHIN proxy.
Imported Issue. Original Details: Jira Issue Key: MIRTH-3837 Reporter: dans Created: 2015-11-17T10:42:46.000-0800