Open rbeckman-nextgen opened 4 years ago
Just tested, works perfectly fine for me using Java 8u71.
Imported Comment. Original Details: Author: narupley Created: 2016-05-26T12:36:53.000-0700
Sorry, forgot to mention that this is in Java 8 u91
Imported Comment. Original Details: Author: jeffreyw Created: 2016-05-26T13:06:07.000-0700
Tested in 8u91 and works there too
Imported Comment. Original Details: Author: narupley Created: 2016-05-26T15:05:47.000-0700
Have exactly the same problem. Using Mirth 3.4.1 and Java 8u71. Works fine using Mirth 3.4.1 and Java 7u72.
Imported Comment. Original Details: Author: nils Created: 2016-08-16T04:16:15.000-0700
Have exactly the same problem. Using Mirth 3.4.2.8129 and Java 1.8.0_51 Any solutions or work around ? Time to solve this issue ? Thanks
Imported Comment. Original Details: Author: ejimenez Created: 2017-04-04T07:49:02.000-0700
I am having the same problem. I use Mirth 3.5.0 and java 1.8.0_131
Already tried BIND SOAP 1.1. But problem persists! Thanks
Imported Comment. Original Details: Author: turanga_fry Created: 2017-08-14T08:27:57.000-0700
Any news about this? I'm facing this problem on Mirth 3.5.1 and java 1.8.0_51
Imported Comment. Original Details: Author: fzenha Created: 2018-06-14T10:01:08.000-0700
When attempting to send in XML as literals through the Web Service Listener, Mirth Connect produces blank messages with Java 8. The suspicion is that Java 8 had more stringent requirements for SOAP bodies than Java 7 did, and as a result processes the data as XML even when using literals or the CDATA tag.