Mirth Connect uses the XStream library to serialize and deserialize objects. It is a potential security risk to allow unexpected object types to be processed through XStream. Therefore we are now being more restrictive about what types are allowed by using an allowlist instead of a denylist. The...
This wasy we can also utilize XStream for pojo (de-)serialization. package com.kaurpalang.mirthpluginsample.shared.interfaces; import com.kaurpalang.mirth.annotationsplugin.annotation.ApiProvider; import com.kaurpalang.mirth.annotationsplugin.type.ApiProviderType; import com.kaurpalang.mirthpluginsample....
XStream 1.3 does not support Java 7. Here are a couple issues that occur in Mirth Connect: When executing a "Test Read" from the Administrator: com.thoughtworks.xstream.converters.ConversionException: Cannot construct XXXXXXXXX as it does not have a no-args constructor On first startup: ERROR...
Jira Issue Key: MIRTH-3135 Reporter: narupley Created: 2014-01-31T16:11:52.000-0800 rbeckman-nextgenadded this to the3.0.2milestoneMay 11, 2020 CollaboratorAuthor I removed the custom StringConverter we're creating, and instead just let XStream create its own. Pushed those changes to the app...
at com.mirth.connect.model.converters.MigratableConverter.unmarshal(MigratableConverter.java:101) at com.mirth.connect.model.converters.ChannelConverter.unmarshal(ChannelConverter.java:79) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) ...